Page MenuHomePhabricator

Stick the edit-in-sequence bar to the top of the window
Open, Needs TriagePublicFeature


Feature summary (what you would like to be able to do and where):
On wikisource, the new extension edit-in-sequence (Documentation) have a toolbar displayed at the top of the page. This bar should stick to the top of the screen to be always visible even if you scroll down (same way as the edition toolbar works with the VisualEditor).

Use case(s) (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):
For now, every time you want to save a page after correction using that tool, you have to scroll back up to have access to the save button. It's not ergonomic and make lost a lot of time. Having the bar following us during scroll would me more practical.

Benefits (why should this be implemented?):
This would improve usability of this extension as it allow to save a page without having to scroll back up after correction.

Event Timeline

M0tty updated the task description. (Show Details)

This is maybe a subtask of T308098

Just as a curio, I had the same problem with the editing toolbar in the 2010 wikieditor and fixed it by sticking the following in my common.css:

/* Make editing toolbar sticky. */
div.wikiEditor-ui div.wikiEditor-ui-top {
	position: sticky;
	top: 0;
	z-index: 999;

(the over-specific selectors is to override the upstream styles)

And as a digression, this problem is why I'm hoping EIS will amass a "full screen editing" feature at some point. As it stands, the PRP Page: user interface contains way too many independently scrollable parts, and necessary controls both above and below the main editing box. A full-screen mode where all UI is constrained within 100vh, and the only thing that scrolls is the main text box, and where any controls are pinned to the top or bottom of the viewport (or the sides, if necessary) would be a great relief. It needs to be combined with EIS because the navigation controls etc. are going to be a problem if you try to do it in base PRP.

But, yeah, a digression on this task…