#21301 closed defect (bug) (invalid)
Disable selecting element when clicking the widget area
Reported by: | alexvorn2 | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.4.1 |
Component: | Widgets | Keywords: | |
Focuses: | Cc: |
Description
http://wpimpact.com/wp-content/uploads/2012/07/Untitled-8.png
when clicking multiple times in Chrome the element is selected in blue color, this should not happen, maybe to add some CSS or jQuery codes, if I will find the solution I will post here.
Change History (4)
#2
follow-up:
↓ 4
@
12 years ago
- Resolution set to invalid
- Status changed from new to closed
yes, but in Firefox and IE 9 this is not happening, and...
really it's something strange that I want to improve this open source project a little and I can't... no more tickets from me
#4
in reply to:
↑ 2
@
12 years ago
- Milestone Awaiting Review deleted
Replying to alexvorn2:
yes, but in Firefox and IE 9 this is not happening
Right - Firefox and IE highlight selections differently than Webkit does. It seems like overkill to try to control just that one funny looking selection with CSS or even JS when it's the browser's default behavior.
really it's something strange that I want to improve this open source project a little and I can't... no more tickets from me
Not sure what's going on with this statement, but if you are feeling unhappy that some of your tickets end up being duplicates or otherwise closed, I hope that you don't think of it as something personal or that what you are suggesting is unintelligent or wrong. Nobody has every single ticket or patch they submit go into core - sometimes suggestions just don't work out, and sometimes there needs to be some discussion to figure that out.
Seems to me that you were given props just the other day, even, so you've already helped make things better, and there's no reason not to keep doing so.
Why shouldn't that happen if you've selected/highlighted something? The way Webkit highlights selections is pretty liberal, but that doesn't mean that it's a bug in either the browser or WordPress.