1076657, 1077515, 1077528, 1079157, 1082017, 1083134, 1083848, 1090329, 1093684, 1096224, 1097128, 1102406, 1105268, 1107960, 1108067, 1108071, 1108923, 1111517, 1111944, 1114329, 1115916, 1118943, 1119475, 1119770, 1120101, 1120102, 1124661, 1126420, 1130936, 1131994, 1134598, 1134849, 1136557, 1139646
This is intended to be the bug where we'll toggle the layout.css.vertical-text.enabled pref to true, so that vertical writing mode can actually be used. This will not be the end of work on vertical writing mode, as the initial release will not support vertical mode for all elements or CSS constructs; e.g. tables, grid, form controls, etc., etc., may be horizontal-only at first. Add "depends on" references here for the vertical writing-mode bugs that are essential to fix before we can usefully enable the feature. Additional aspects of vertical support that we want to implement eventually, but that need not block the initial release, should be marked as blocking (directly or indirectly) the main writing-mode bug instead of this one.
Here's the patch to enable writing-mode; we're not ready to consider landing this yet, though.
Assignee: nobody → jfkthame
Status: NEW → ASSIGNED
4 years ago
Depends on: 1122253
4 years ago
Depends on: 1130935
Depends on: 1130936
Depends on: 1130937
Note that the patch in bug 1082017 will need to land together with this bug, otherwise we'll get mochitest failures. (But it can't land earlier, because it depends on writing-mode being supported.)
(In reply to Jonathan Kew (:jfkthame) from comment #2) > Note that the patch in bug 1082017 will need to land together with this bug, > otherwise we'll get mochitest failures. (But it can't land earlier, because > it depends on writing-mode being supported.) This is no longer an issue, as that patch was modified so as to land safely, independently of the pref change here.
Time to consider flipping the pref on non-release channels (nightly/dev), so that we can begin to get wider testing of what's been implemented so far? This will also mean that the writing-mode tests start running on mozilla-central, which IMO is highly desirable.
Attachment #8522865 - Attachment is obsolete: true
If we do bug 1134598 separately, then all that's left here is the pref change.
Attachment #8566488 - Flags: review?(smontagu)
As per discussion with jet/dbaron/heycam today, the proposal is to do this *after* next week's uplift.
... #ifndef RELEASE_BUILD, that is. With notification to firefox-dev and dev-gaia that it's enabled for nightly/aurora only, so they shouldn't depend on it yet.
Attachment #8566488 - Flags: review?(smontagu) → review+
Alias: enable-writing-mode → enable-writing-mode-dev
Summary: enable CSS writing-mode support → enable CSS writing-mode support in developer channels
Tracking for Firefox 39.
tracking-firefox39: --- → +
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
status-firefox39: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla39
Release Note Request (optional, but appreciated) [Why is this notable]: Cool new feature on dev channels. [Suggested wording]: Vertical text mode enabled by default on Developer Edition [Links (documentation, blog post, etc)]: https://developer.mozilla.org/en-US/docs/Web/CSS/writing-mode
relnote-firefox: --- → 39+
Jonathan, is this likely to stay enabled or be turned off when 39 moves to beta? Would exploratory testing help or does this need the automated tests for us to feel that it's ready for release? Thanks.
For 39, and probably another cycle or two, it'll stay disabled on beta/release channels. (The pref is subject to #ifdef RELEASE_BUILD in all.js.) Bug 1138384 will track enabling the feature on release. (It's not primarily a question of testing, but of feature completeness: there are some substantial parts of CSS layout that do not yet handle vertical mode, such as tables.)
Updated: https://developer.mozilla.org/en-US/docs/Web/CSS/writing-mode and https://developer.mozilla.org/en-US/Firefox/Releases/39#CSS
Keywords: dev-doc-needed → dev-doc-complete
You need to log in before you can comment on or make changes to this bug.