#19357 closed defect (bug) (fixed)
Pointers misplaced when object is hidden
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 3.3 | Priority: | low |
| Severity: | minor | Version: | 3.3 |
| Component: | UI | Keywords: | has-patch |
| Focuses: | Cc: |
Description
I got a small issue with the new pointers (media upload pointer). It was hiding behind the admin bar since I had the editor hidden trough CSS. Probably a case that is not likely to see for a lot of users
Attachments (1)
Change History (16)
#3
@
14 years ago
I do need it on the edit page but only when a tab is selected. This due some possible large meta_boxes.
The reason I post it as a bug is due the possibility that in other rare cases this can happen.
#5
in reply to:
↑ 1
@
14 years ago
Replying to scribu:
You can hide the editor by modifying the 'supports' parameter of the post type.
Not valid if you want to hide it temporarily. I can imagine some kind of 'wizard like' (been there, done that) way of creating pages, where you only want to show the editor after entering the title. The editor won't be visible at page load, so the pointer can't be placed at the correct position. Simple as pie: If the target object is not there, the pointer shouldn't be placed.
#6
follow-up:
↓ 7
@
14 years ago
Yes, except in this case, the DOM element is there, but it's hidden.
#7
in reply to:
↑ 6
@
14 years ago
Replying to scribu:
Yes, except in this case, the DOM element is there, but it's hidden.
Correct, but it doesn't make sense to show a pointer at a hidden element. Look at it from an user perspective, seeing pointers where the element is hidden, doesn't make sense. I agree that it isn't easy to fix and not a lot of users will have to face it, but problem lies in the base of the way pointers work.
#8
@
14 years ago
I agree with Coen. We should simply ensure that a pointer's target element is visible first.
#9
@
14 years ago
- Keywords needs-patch added
- Milestone changed from Awaiting Review to 3.3
- Priority changed from normal to low
You can hide the editor by modifying the 'supports' parameter of the post type.
I suggest closing as 'worksforme', unless there's potential to make the pointer JS more robust.