Symphony.

When you try and edit a datasource in Chrome, it doesn't work and the list of output elements is missing.

A datasource I created in Chrome didn't return anything on a frontend page.

I can't seem to reproduce your issue (Chrome 11.x on ArchLinux). Any further details? I.e. Chrome version, OS, etc.

Likewise, Chrome 11.x on OSX.

Do you have any extensions that inject Javascript installed? It's possible that they are breaking the Javascript on that page, check your Console :)

There was an old (by old I mean maybe a year ago) bug in Safari which hid options in multi-select boxes. But I'm pretty sure that was fixed.

Was the entire select box gone, or just the options within?

Without further information by June 8th, this issue will be closed.

I only see the same issue as the Safari issue mentioned by Nick. When the page is loaded, nothing can be seen in the multiselect. You have to click in the srollbar (resp. the scrollbar arrows) or scroll up inside the multiselect using your touchpad (whatever) to make the options suddenly appear.

A datasource I created in Chrome didn't return anything on a frontend page.

I can not replicate this.

When the page is loaded, nothing can be seen in the multiselect.

I think this only happens when the select options are "overflowing" the box and I guess it has to do with the way Symphony removes and adds the options based on the source selection. Maybe we can finally fix this in Symphony 2.3 where a few things have to be adjusted to make this selection process bulletproof.

I only see the same issue as the Safari issue mentioned by Nick. When the page is loaded, nothing can be seen in the multiselect. You have to click in the srollbar (resp. the scrollbar arrows) or scroll up inside the multiselect using your touchpad (whatever) to make the options suddenly appear.

Now that I think of it, I had the same problem with an older version of Chrome but it seems fixed now.

So consensus on this that older versions of Chrome had an issue, but that's now resolved, and considering Chrome auto updates, we can close and forget?

I don't see that the issue is resolved. Not in Chrome (latest) nor in Safari (latest). As Nils mentioned, it only occurs when the options "overflow" the box (which will be pretty standard on complicated websites.) To me this issue is a bit annoying.

The question is: Does this happen because Symphony delivers suboptimal code? Or is it because Chrome/Safari are simply buggy?

[EDIT]: Attached Chrome screenshot.

Attachments:

Bildschirmfoto 2011-06-10 um 10.19.42.png

I can't reproduce in Chrome 12.0.742.91 or Safari 5.0.5 on Mac OSX.

The issue don't manifest when editing a datasource or creating a new one.

Are there any extensions installed that are adding JS or CSS to the backend page when the issue arises?

Can it be reliably reproduced? If so, what are the steps?

Attachments:

Screen shot 2011-06-10 at 7.21.20 PM.png

I can't reproduce in Chrome 12.0.742.91 or Safari 5.0.5 on Mac OSX.

Same here (Chrome 12 on ArchLinux). Perhaps it's a Webkit bug...

I can confirm the issue using lasted Safari on a German localised Mac. If you hover over the selectbox and scroll down, the options will be displayed again so I'm quite sure it's a conflict with the admin JavaScript.

Right.

I can reproduce this if I set my logged in author to use German instead of English. So this issue seems to only trigger when Symphony is localised.

EDIT I can't get this to occur in Chrome, only Safari. I also cannot repeat the issue on the Event Editor (with the filters overflowing). Also, I can only get it to occur randomly, which is painful for trying to test and verify it. Does it happen every time for you Nils? If you update jQuery to something newer, does that solve the issue?

Please try it in the datasource editor. Use a section which has lots of fields.

For me it happens consistently in Safari 5.0.5 on OS X 10.6.7, no matter if my Mac is English or German, no matter if Symphony is localized or not (i.e. any language extensions uninstalled). This issue is so old that you must be able to reproduce it even on older Macs.

Yeah I still can't get it happen reliably in Safari 5.0.5 on OSX 10.6.7. It happens sometimes, I wonder if the actual field names has something to do with it as well.

This is strange, because it always happens for me, since a long time. I have no idea what could make the difference.

I copied the whole "Included Elements" label element of the DS editor (including the select and the optgroups) to a vanilla HTML file — it renders fine then.

Should we make a test with super-simple fieldnames?

OK, I copied the stylesheets and the JS to my vanilla test file. Hard to believe what happens.

The CSS files don't make a big difference. But I have seven Symphony JS files:

<script type="text/javascript" src="http://example.com/symphony/assets/symphony.collapsible.js"></script>
<script type="text/javascript" src="http://example.com/symphony/assets/symphony.orderable.js"></script>
<script type="text/javascript" src="http://example.com/symphony/assets/symphony.selectable.js"></script>
<script type="text/javascript" src="http://example.com/symphony/assets/symphony.duplicator.js"></script>
<script type="text/javascript" src="http://example.com/symphony/assets/symphony.tags.js"></script>
<script type="text/javascript" src="http://example.com/symphony/assets/symphony.pickable.js"></script>
<script type="text/javascript" src="http://example.com/symphony/assets/admin.js"></script>

As soon as I remove one of them (no matter which one), the issue is fixed.

Can anyone confirm this?

OK, obviously JavaScript breaks at some point if you remove any of these files. So we still don't know what exactly renders the issue. But we can be rather sure that it is caused by JavaScript.

I can confirm this issue in both Safari and Chrome. And I found a solution.

I can't point to any resources, but I believe the multi select box just needs to be redrawn to show the options. This can be done by either focus()-ing the select box (not good, because it gets focussed) or by setting its size attribute. The multi select box mustn't have a size attribute set in the original HTML and it mustn't have a 'height' set via CSS. ('min-height' is OK, I think as long it doesn't coincidently equals the calculated height via the size attribute.)

So a solution could be https://github.com/symphonycms/symphony-2/pull/686. As a side-effect some multi select boxes might have different heights, depending on the number of their options. This could be avoided by specifically changing the multi select CSS only in the DS editor.

Confirmed. The issue is fixed with this pull request. Thanks, @klaftertief!