You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on Apr 12, 2024. It is now read-only.
I can't reproduce this in FF 28. 1.2.14 / 1.2.15 look the same. Which browser did you test? There was a fix for a Firefox ngOptions render bug, maybe this is related. f40f54c
@yappli I am able to reproduce this with Chrome 33 and OSX 10.9 and it does look like a browser bug.
The easiest workaround I was able to find is to change the attribute require to ng-required="true"
The reason I couldn't reproduce it is because you posted an example of the working build, not of the broken build. This is bad, don't do this, it's not helpful. Especially on jsfiddle where the UI doesn't make it obvious that you're using the working build!
So yes, there is a regression from the fix to break the problem in Firefox. Someone should look into this, PRs welcome, although I suppose there is a workaround to fix this.
Activity
Narretz commentedon Mar 25, 2014
I can't reproduce this in FF 28. 1.2.14 / 1.2.15 look the same. Which browser did you test? There was a fix for a Firefox ngOptions render bug, maybe this is related. f40f54c
GabrielDelepine commentedon Mar 25, 2014
Sorry, I forgot to mention this.
Chrome 30 : bug
Chromium 32 : bug
Firefox 27 : no bug
caitp commentedon Mar 25, 2014
WFM in Chrome stable
GabrielDelepine commentedon Mar 25, 2014
I just update to Chromium 33 and I still have the issue.
caitp commentedon Mar 25, 2014
Do you have all your extensions disabled when testing?
GabrielDelepine commentedon Mar 25, 2014
@caitp Yes, all extensions disabled and with the incognito mode of chrome. My OS is Ubuntu.
Chromium = Ubuntu repo
Chrome = Google repo
I also tried with Chrome under W7 (fresh install) and this bug also ! See this screenshot
IE11 doesn't bug
caitp commentedon Mar 25, 2014
I can't reproduce on OSX 10.9 or Windows 8.1 with Chrome 33. You should investigate it, but it's possibly a browser bug.
lgalfaso commentedon Mar 25, 2014
@yappli I am able to reproduce this with Chrome 33 and OSX 10.9 and it does look like a browser bug.
The easiest workaround I was able to find is to change the attribute
requiretong-required="true"GabrielDelepine commentedon Mar 25, 2014
@lgalfaso : Your workaround works for me, thanks.
I don't know if it's a browser bug or not. Probably.
caitp commentedon Mar 25, 2014
The reason I couldn't reproduce it is because you posted an example of the working build, not of the broken build. This is bad, don't do this, it's not helpful. Especially on jsfiddle where the UI doesn't make it obvious that you're using the working build!
So yes, there is a regression from the fix to break the problem in Firefox. Someone should look into this, PRs welcome, although I suppose there is a workaround to fix this.
26 remaining items
fix(select): auto-select new option that is marked as selected
fix(select): auto-select new option that is marked as selected
fix(select): auto-select new option that is marked as selected