7155 2006-02-09 06:28:30 -0800 TinyMCE: Selection lost when clicking on <select> element. 2008-02-29 16:51:56 -0800 1 1 1 Unclassified WebKit HTML Editing 420+ Mac OS X 10.4 RESOLVED FIXED http://tinymce.moxiecode.com HasReduction P3 Major --- 6627 1 spam webkit-unassigned ian lweintraub mozillabug321 webkit oldest_to_newest 31943 0 spam 2006-02-09 06:28:30 -0800 Expected Results: When a selection is made and the <select> element activated (to show dropdown) the selection should remain, just as when you do something with a popup window. What I got: Selection is lost instead of "grayed" out like when a popup is made. Steps to reproduce: 1) Go to http://tinymce.moxiecode.com/example.php?example=true 2) Select some text, click on one of the dropdowns for selecting font/fontsize etc. 3) The selection is lost. Try the same thing but with clicking on the color selector for a popup or similar, selection is left in the background but grayed out. You should probably construct your own testcase, since the current version has some workarounds implemented for this (for older Safari versions). 32022 1 aldo 2006-02-10 04:55:38 -0800 See http://hoeben.net/files/webkit/repro7155.html for a simple repro document. Selection in the contenteditable div is cleared when touching the <select> 32464 2 6481 joost 2006-02-14 04:13:04 -0800 Created attachment 6481 Testcase Added Aldo's testcase to the bug itself. 52454 3 mjs 2006-08-12 22:53:29 -0700 Seems to work with dev versions of TinyMCE, for example http://tinymce.moxiecode.com/test/examples/example_full.htm 3263 4 ted 2007-07-31 23:26:44 -0700 Tested with Safari 3.0.3 on OS X. This is still a valid bug. However, I did notice something interesting in the details. The first time you click on any given drop down menu, the selection is eradicated. However, any subsequent clicks on that same menu, the selection is sustained. I do not know if this was the case prior to 3.0.3. 70118 5 webkit 2008-02-10 13:03:14 -0800 I've tested the test case in Webkit r30119 and I don't see buggy behavior. Is it fixed? Any confirmations? 72407 6 mrowe 2008-02-29 16:51:56 -0800 The behaviour of TOT on the attached test case matches that of Firefox 2. Firefox 3 appears to have regressed and exhibits similar behaviour to that attributed to WebKit in the original report. Closing as FIXED as we now match the reporter's expectations. 6481 2006-02-14 04:13:04 -0800 2006-02-14 04:13:04 -0800 Testcase Webkit bugzilla repro movie- #7155.html text/html 625 joost PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4KPEhUTUw+CjxIRUFEPgo8VElUTEU+IFdlYmtpdCBidWd6aWxsYSByZXBybyBtb3ZpZTog IzcxNTUgPC9USVRMRT4KPE1FVEEgTkFNRT0iQXV0aG9yIiBDT05URU5UPSJBbGRvIEhvZWJlbiI+ CjxzdHlsZSB0eXBlPSJ0ZXh0L2NzcyI+CiNlZGl0YWJsZSB7CiAgd2lkdGg6IDQwZW07CiAgaGVp Z2h0OiAxMGVtOwogIGJvcmRlcjogMXB4IHNvbGlkIGJsYWNrOwp9CjwvU1RZTEU+CjwvSEVBRD4K CjxCT0RZPgo8UD5SZXBybyBtb3ZpZSBmb3IgYnVnIDxhIGhyZWY9Imh0dHA6Ly9idWd6aWxsYS5v cGVuZGFyd2luLm9yZy9zaG93X2J1Zy5jZ2k/aWQ9NzE1NSI+IzcxNTU8L2E+PC9QPgoKPGRpdiBp ZD0iZWRpdGFibGUiIGNvbnRlbnRFZGl0YWJsZT0idHJ1ZSI+CiAgPHA+VGVzdCBjb250ZW50PC9w Pgo8L2Rpdj4KCjxmb3JtPgo8c2VsZWN0IG5hbWU9InRlc3QiPgo8b3B0aW9uIHZhbHVlPSJ0ZXN0 MSI+MQo8b3B0aW9uIHZhbHVlPSJ0ZXN0MiI+Mgo8b3B0aW9uIHZhbHVlPSJ0ZXN0MyI+Mwo8b3B0 aW9uIHZhbHVlPSJ0ZXN0NCI+NAo8L3NlbGVjdD4KPC9mb3JtPgoKPC9CT0RZPgo8L0hUTUw+Cg==