#6054 closed defect (bug) (fixed)
"Saved at [time]" status box shouldn't shift page
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 2.5 | Priority: | normal |
| Severity: | normal | Version: | 2.5 |
| Component: | General | Keywords: | has-patch has-unit-tests |
| Focuses: | Cc: |
Description
"Saved at [time]" status box shouldn't shift page
ENV: WP trunk r7117
I don't know if this is only because it isn't styled yet.
"Saved at [time]" status box shouldn't shift parts of the page down. This is distracting for a person. It should appear in an existing space for it.
Attachments (1)
Change History (9)
#2
@
18 years ago
How about we put it in the sidebar?
It was under the post box before because that's where the save buttons were. Now the save buttons are in the sidebar, so autosave notices should go there too.
Attached make the message more subtle and puts it by the save buttons. It shifts the layout of the sidebar a bit still. Good? Bad? The sidebar is also shifted a bit when the preview link is added; this has been the case for a while.
The main content layout is still shifted a bit by the permalink line. This also has been the case for a while.
#3
@
18 years ago
- Keywords has-patch added
mdawaffe, I think this addresses the issue, primarily by being more subtle, but it is also good to have it in the vicinity to have the state near the Save button, b/c that matches expectations and is common in other applications.
This ticket was mentioned in PR #6203 on WordPress/wordpress-develop by @dmsnell.
2 years ago
#7
- Keywords has-unit-tests added
Alternative to #6054
When reaching text nodes that require creating elements during active format reconstruction, aborts the HTML Processor.
This prevents progressing into a document where the text nodes would change the structure and affect breadcrumbs. Until the HTML Processor properly supports text nodes this makes it possible to continue operating safely.
But is it distracting for a robot? I think not.
Maybe iammattthomas can advise.