using webkit-transform causes drop downs to be hidden

When using webkit-transform and Chrome with CKEditor the drop down menus can be hidden.

It seems that using webkit-transform can have unexpected z-index consequences which in turn hides the drop down menus.

The soloution is to add -webkit-transform:translate3d(0,0,0) to any element that might fall under this influence.

However the solution does not work when using the maximize button.

Tue, 03/11/2014 - 13:11

sebstefanov

Joined: 03/02/2012

Posts: 1329

The request got lost in the

The request got lost in the laundry list of other stuff. It's a good idea to bump requests on occasion, to show devs there's still interest.

Customer and Community Manager, CKSource
Follow us on: Facebook, Twitter, LinkedIn

If you think you found a bug in CKEditor, read this!

Tue, 03/11/2014 - 18:09

(Reply to #2) #3

RObWilkinson

Joined: 20/02/2014

Posts: 8

Bumping Requests

How does one "bump" requests?

Wed, 03/12/2014 - 11:27

sebstefanov

Joined: 03/02/2012

Posts: 1329

Sorry, the bump thing was for

Sorry, the bump thing was for another post (had multiple tabs open). Here's what Reinmar (dev) said about your issue:

There are two options:

Something is broken in Chrome regarding transformations and z-indexes or focus or whathever. This is probable because transformations (especially 3d) are a new feature and using them together with other advanced stuff like iframes might not be yet implemented well enough.
CKEditor is somehow lost because of transformation. Some property / computed style may return a different but still correct value which CKEditor does not handle properly. But to debug this we would need to have a test case, which wasn't provided.

Customer and Community Manager, CKSource
Follow us on: Facebook, Twitter, LinkedIn

If you think you found a bug in CKEditor, read this!

Wed, 03/12/2014 - 14:05

(Reply to #4) #5

RObWilkinson

Joined: 20/02/2014

Posts: 8

Yes. I can appreciate that a test case is required. I spent some time trying to create one yesterday but as yet do not have a satisfactory one. I have been able to work around all but the maximize button case by adding the -webkit-transform:translate3d(0,0,0) fix to the higher level div. I am not sure that is satisfactory from a performance perspective but at least for now it gets it working.

I tend to agree with you that chrome is broken in this area. I dont see why higher level transforms should blow away the z-indexing below it.

I will see if I can carve out further time to generate a test case.

Regards,

Rob