Closed
Bug 887749
Opened 12 years ago
Closed 12 years ago
Fluid width for translation interface
Categories
(developer.mozilla.org Graveyard :: Design, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: regagnon, Unassigned)
References
Details
(Whiteboard: [specification][type:change])
Attachments
(1 file)
|
291.27 KB,
image/png
|
Details |
What feature should be changed? Please provide the URL of the feature if possible.
==================================================================================
The translation interface should have a fluid width. The current width is OK for English content creation. But with the split interface for translation, translating some content (like large tables) are near to impossible.
What problems would this solve?
===============================
It would allow to see the entire content that need to be translated.
Who would use this?
===================
Translators with large screens could profit from this change
What would users see?
=====================
Fluid width.
What would users do? What would happen as a result?
===================================================
Provide a button to switch from the fixed width to the fluid width, and vice versa.
Or change the width to be always fluid.
Is there anything else we should know?
======================================
| Reporter | ||
Comment 1•12 years ago
|
||
Comment 2•12 years ago
|
||
We'll keep this in mind with the upcoming redesign.
Updated•12 years ago
|
Component: General → Design / user experience
Updated•12 years ago
|
Comment 3•12 years ago
|
||
I did move MDN to fluid width so this is now complete.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 4•12 years ago
|
||
I am sorry bu I disagree. There is max-width on the page content. When translating some pages on a 27" display, you miss the empty space.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Updated•12 years ago
|
Flags: needinfo?(dwalsh)
Comment 5•12 years ago
|
||
discussed in triage meeting on 1/10/2014. Getting into dev queue, should be possible to do this per David Walsh.
Updated•12 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 6•12 years ago
|
||
This can be implemented once prioritized.
Updated•12 years ago
|
Flags: needinfo?(dwalsh)
Comment 7•12 years ago
|
||
Yes, even if thinking/planning/designing of better l10n tools are about to start, I think this should be done to ease it in the meantime. I'm proposing P1 because it may have no more meaning if we wait Q2 for this (depending of the results of the l10n planning).
Feedbacking ali and mars for the priority.
Flags: needinfo?(mars)
Flags: needinfo?(aspivak)
Comment 8•12 years ago
|
||
I'm going to set this to P1, since Ali already mentioned moving it into the queue in comment 5.
Flags: needinfo?(mars)
Flags: needinfo?(aspivak)
Priority: -- → P1
Comment 9•12 years ago
|
||
Commits pushed to master at https://github.com/mozilla/kuma
https://github.com/mozilla/kuma/commit/50ca920eae2e5cd82804fc6725aa3f9af0cd53cf
fix bug 887749 - Make translate page more fluid
https://github.com/mozilla/kuma/commit/9bda61f3ea1d89a2b53d23ac49f77d051d263339
Merge pull request #1943 from darkwing/fluid-translation-887749
fix bug 887749 - Make translate page more fluid
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•