Home/ Questions/Q 8462315
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-10T14:07:57+00:00

This is actually an issue sorted out from another SO question . In the

  • 0

This is actually an issue sorted out from another SO question.

In the jsFiddle example here http://jsfiddle.net/5WrcD/2/show/ when you change one select the other one gets the value synchronised. Please try this with Firebug on and both select menus expanded.

When you first load the page and change first select to 20, the selected="selected" on both becomes 20 in DOM, but not shown in display.

Any idea on why this is happening?

The example uses Ember.js library, but anyway the display is supposed to reflect the DOM state right?

This bug only happens in Firefox, this is a Firefox specific question

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Works in Chrome/Safari, not in FF. Perhaps these two Ember.js warnings mean something:

    1. WARNING: Computed properties will soon be cacheable by default. To enable this in your app, set ENV.CP_DEFAULT_CACHEABLE = true.
      ember-0.9.8.1.js (line 65)

    2. WARNING: The way that the {{view}} helper affects templates is about to change. Previously, templates inside child views would use the new view as the context. Soon, views will preserve their parent context when rendering their template. You can opt-in early to the new behavior by setting ENV.VIEW_PRESERVES_CONTEXT = true. For more information, see https://gist.github.com/2494968. You should update your templates as soon as possible; this default will change soon, and the option will be eliminated entirely before the 1.0 release.

    Update #1:

    It looks like turning off all the selected (after the elements have been created) also helps. Attach to the end of your script:

    setTimeout( function (){ $('option').prop('selected',false); } , 100 );
// Anonymized as per Fabrício Matté's suggestion

    Note: There may be a callback you can do it in, instead of running it automatically 100ms after.

    Update #2:

    It also looks like instead of setting the properties of the option, you can remove the content of the Ember creation:

    App.myController = Ember.Object.create({
   //content: 10    /* comment out, remove, or set to '' instead of 10 */
});

    Note: I do not use Ember, so I don’t know if this would effect anything

    • 0