Closed
Bug 790789
Opened 12 years ago
Closed 12 years ago
Editor window too narrow
Categories
(support.mozilla.org :: Knowledge Base Software, task, P2)
support.mozilla.org
Knowledge Base Software
Tracking
(Not tracked)
RESOLVED
FIXED
2012Q4
People
(Reporter: atopal, Assigned: rrosario)
References
Details
(Whiteboard: u=contributor c=wiki p=2 s=2012.21)
Attachments
(1 file)
738.41 KB,
image/png
|
Details |
No description provided.
Reporter | ||
Comment 1•12 years ago
|
||
As I localizer I would like to have a better editing experience with a wider editor. https://sumo.etherpad.mozilla.org/110
Comment 2•12 years ago
|
||
The new editor will occupy the whole column, with the “For Contributors” sidebar moved up top above the editor. This is similar to how the current top page operate: no sidebar, with the sidebar located on top.
Assignee | ||
Comment 3•12 years ago
|
||
(In reply to Bram Pitoyo [:bram] from comment #2) > The new editor will occupy the whole column, with the “For Contributors” > sidebar moved up top above the editor. This is similar to how the current > top page operate: no sidebar, with the sidebar located on top. Not for translating? Or what are you referring to? Maybe I haven't seen the mockups.
Comment 4•12 years ago
|
||
(In reply to Ricky Rosario [:rrosario, :r1cky] from comment #3) > Not for translating? Or what are you referring to? Maybe I haven't seen the > mockups. For both editing and translating. I don’t know if the en-US editing interface will benefit from a wider interface like this, but if it does, then we should change it so that every editing interface is one-column. Attached is a mockup from the pt-BR translation interface. What I did was change the #localize-document article id to be inside a .grid_12 div. Then I put the two sidebars up top, inside a .feature-box div. I also resized the column width to 49% so they fill half the page, and textarea width to 100%, so they fill the whole half of the column. Lastly, I set the width for the textareas inside the .approved and .localized div classes to 95%, rather than 100%. This prevents collision.
Assignee | ||
Comment 5•12 years ago
|
||
Adding to next sprint. This needs some exploration, => 2pt
Whiteboard: u=contributor c=wiki p= → u=contributor c=wiki p=2 s=2012.20
Assignee | ||
Updated•12 years ago
|
Priority: -- → P2
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → rrosario
Assignee | ||
Comment 6•12 years ago
|
||
I didn't get to this in 2012.20, the diff took way longer than expected. Pushing to 2012.21.
Whiteboard: u=contributor c=wiki p=2 s=2012.20 → u=contributor c=wiki p=2 s=2012.21
Assignee | ||
Comment 7•12 years ago
|
||
Landed and deployed: https://github.com/mozilla/kitsune/commit/d0d6c7dd8446c0142ba3484592bef086ac6202ee
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 8•12 years ago
|
||
I like the way you implemented this. The only issue I can see is that the preview is now shown in the wide screen format too, and that might cause issues where things look okay in the wide screen format, but not with the narrower view of the normal article view. I'm not going to file a new bug for that though. Waiting on localizer feedback instead.
Assignee | ||
Comment 9•12 years ago
|
||
(In reply to Kadir Topal [:atopal] from comment #8) > I like the way you implemented this. The only issue I can see is that the > preview is now shown in the wide screen format too, and that might cause > issues where things look okay in the wide screen format, but not with the > narrower view of the normal article view. I'm not going to file a new bug > for that though. Waiting on localizer feedback instead. Good point, we should limit the width of the preview to the actual width in the article page.
Comment 10•12 years ago
|
||
I am not sure if, to make it as representative as possible, the text inside the preview box should also be set with the same font size and style as the text on the article page?
Reporter | ||
Comment 11•12 years ago
|
||
Yeah, ideally the preview looks exactly like the final view.
You need to log in
before you can comment on or make changes to this bug.
Description
•