Asset builder WYSYWIG field and IE9

(Eric) #1

Hi all,

 

Our IT rolling out new computers and as part of this process we will now have IE9 as a standard browser.

We use several asset builders on our website and it appears that a WYSYWIG field on an asset builder totally screws up. When pasting text longer then hight of the field, text acts like a div with overflow:visible as opposed to creating scroll bars. With other fields below covering the text it is impossible to edit.

 

This doesn't happen in admin interface, only in asset builders. Are these WYSYWIG fields different and is there any fix (other then turning on compatibility mode in a browser)?

 

We use 4.10.1 SquizMatrix

 

(Robin Shi) #2

The asset builder is in the front end, is it HTML4 or HTML5?

(Eric) #3

HTML5, although we have tried to add different doc types and it didn't work. Compatibility view fixes the issue. It is a specially weird since it works fine in IE8 without compatibility view on.

(Robin Shi) #4

Yes, Compat View is one of the most evil thing from IE because there is not sufficient documentation describing what restriction it brings to JavaScript. You are luckier than us, in our case, HTML5 kills WIYSIWYG in simple editing interface whole lot.

(Nic Hubbard) #5

Sounds like you guys need to submit a bug report.

(Robin Shi) #6

Not quite necessary Nic. The simple editing interface is quite old and should retire.

We are moving onto Edit+ parse file by parse file.

(Eric) #7

I disagree. You can't just replace WYSYWIG field with Edit+/Viper (That would be great) and this is a public asset builder. More importantly even for internal use it is much simpler to create an asset builder that exposes needed metadata fields in one form instead of training employees in use of Edit+.

 

Edit+ is great for content creators if it's part of their job description, but it is way simpler to create asset builder for news, events and any other structured data that anyone who ever filled in form online can do without training (temps, casuals even public), no need to explain where to create assets, no extra buttons, no need to explain what metadata or workflow is, all transparent.

(Robin Shi) #8

I was talking about simple editing interface Eric.

As a workaround, the quick way I can think of is using html4 parsefile to render the builder, then have the builder appearing in a JS pop-up (iFrame), which is better for user experience.

(Eric) #9

I was specifically talking about asset builders though. This problem doesn't seem to effect other parts of the system. It also could be the fact that asset builder creates calendar asset and I have been told long time ago that calendar and news assets use different WYSYWIG, not sure if it is thrue anymore.

 

I am not sure what you mean by HTML4 parsefile? Isn't it controled by Doctype? We tried different doctypes for the builder didn't seem to make a difference.

(Robin Shi) #10

Yes I am talking about DOCTYPE as below,

If the issue only appears in IE9, try below in the parsefile.

(Eric) #11

Thanks tried it not working weird...

(Robin Shi) #12

What will you get if applying a blank design (no css no js linked)?