Summary: | BBCode selector is broken | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Jessica Hawkwell <root> | ||||
Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED DUPLICATE | ||||||
Severity: | Normal | CC: | ahmad.saleem792, ap, bfulgham, mrowe, rniwa | ||||
Priority: | P2 | Keywords: | HasReduction, InRadar | ||||
Version: | 525.x (Safari 3.1) | ||||||
Hardware: | Mac | ||||||
OS: | OS X 10.5 | ||||||
URL: | http://www.varusonline.com/forum/viewtopic.php?t=7988 | ||||||
Attachments: |
|
Description
Jessica Hawkwell
2008-04-25 17:46:05 PDT
Created attachment 20826 [details]
Reduced test case
Other browsers do not appear to fire the change event when programatically setting selectedIndex from within a change event handler.
I am unable to reproduce this issue in Safari 15.6 on macOS 12.5 based on attached test case (If I am understanding it correctly), upon selecting second option from drop-down, it triggers following: Changed! Selected index is now 1. Similarly, all other browsers (Chrome Canary 105 and Firefox Nightly 104) also do same dialog: Changed! Selected index is now 1. Since all browsers are consistent, I think it can be marked as "RESOLVED WONTFIX" or "RESOLVED INVALID". Thanks! |