Bug 18748 - BBCode selector is broken
Summary: BBCode selector is broken
Status: RESOLVED DUPLICATE of bug 23721
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 525.x (Safari 3.1)
Hardware: Mac OS X 10.5
: P2 Normal
Assignee: Nobody
URL: http://www.varusonline.com/forum/view...
Keywords: HasReduction, InRadar
Depends on:
Reported: 2008-04-25 17:46 PDT by Jessica Hawkwell
Modified: 2022-07-22 11:51 PDT (History)
5 users (show)

See Also:

Reduced test case (282 bytes, text/html)
2008-04-25 17:49 PDT, Mark Rowe (bdash)
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jessica Hawkwell 2008-04-25 17:46:05 PDT
When a customer using Safari uses the BBCode dropdown menus, Safari inserts odd things (such as "[*][/*]") into their text.  This breaks custom text formatting.

This issue only occurs on Safari (both Win and Mac), other browsers were tested (Camino, Firefox, Opera, Netscape, MSIE, MSIE7, Konqueror, and Epiphany), but only Safari presents this issue.

Reference URL: http://www.varusonline.com/forum/posting.php?mode=reply&t=675
(Registration not required for bugtracing or previewing the erroneous formatting results)
Comment 1 Mark Rowe (bdash) 2008-04-25 17:49:43 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.
Comment 2 Mark Rowe (bdash) 2008-04-25 17:51:39 PDT
Comment 3 Ahmad Saleem 2022-07-22 07:25:53 PDT
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!
Comment 4 Alexey Proskuryakov 2022-07-22 11:51:11 PDT

*** This bug has been marked as a duplicate of bug 23721 ***