What did you do? ================ 1. Edit any non en-US doc 2. Click the full-screen button What happened? ============== The editor goes in full-screen, but the first line of button tools isn't visible in the viewport. What should have happened? ========================== All the tools in the editor should be visible in the full-screen mode. Is there anything else we should know? ====================================== It works well in non-l10n UI. The button to go back to the non-full-screen mode is on the first line, making impossible to go back to the "normal" mode and so blocks access to save buttons.
Noticed another issue while testing this, so I thought I would generalize the bug report out to include it. In addition to the problem mentioned in comment 0, the Fullscreen button sometimes causes the WYSIWYG toolbar to appear floating on the left side of the screen. For design, the sign off is pretty simple. The Fullscreen button should work exactly as it does on normal pages, without any of the weirdness described in this comment or comment 0.
Summary: l10n editor full-screen can't be reverted → Strange behavior of Fullscreen button on localization edit page
Can I be provided steps to reproduce, or more browser info? I'm not seeing either of the side-effects you are: http://screencast.com/t/XrKMJ9Db7v
Followed the steps provided, can't reproduce. Please provide a screenshot so I know what I'm looking for, or how it can somehow be prevented.
OK, I see it now; didn't have enough content within the WYSIWYG. Will look at now.
Commits pushed to master at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/9b89067777330f28897cd3ea4125669012ea85b0 fix bug 841047 - Fix translation fullscreen issues https://github.com/mozilla/kuma/commit/f050a7f96cb7f3d056b459c39545fa0c0d249b11 Merge pull request #870 from darkwing/fullscreen-841047 fix bug 841047 - Fix translation fullscreen issues
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Good stuff. Go David!
You need to log in before you can comment on or make changes to this bug.