CSS/text-size-adjust: Difference between revisions
< CSS
(stub) |
(revert back to non-spam version) |
||
| (11 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
= CSS text-size-adjust = | |||
This page is for tracking the development of a standard 'text-size-adjust' property. There are | This page is for tracking the development of a standard '<code>text-size-adjust</code>' property. There are three known vendor prefixed implementations of it: <code>[http://dbaron.org/log/20111126-font-inflation -moz-], [http://msdn.microsoft.com/en-us/library/ff462082%28v=vs.92%29.aspx#sectionToggle2 -ms-], [https://developer.apple.com/library/ios/#DOCUMENTATION/AppleApplications/Reference/SafariWebContent/AdjustingtheTextSize/AdjustingtheTextSize.html -webkit-]</code>. | ||
Web developers are using at least 4 prefixed implementations in the wild, including <code>[https://www.google.com/search?q=site%3Agithub.com+%22-o-text-size-adjust%22 -o-text-size-adjust]</code> which Opera does not implement (as of 2012-088 per Florian of Opera on the CSSWG telcon that morning). | |||
See the W3C Editor's Draft: [http://dev.w3.org/csswg/css-size-adjust/ CSS Mobile Text Size Adjustment Module Level 1] | |||
- [[User:Tantek|Tantek]] | |||
__TOC__ | |||
== property definition == | == property definition == | ||
(in | See the W3C Editor's Draft: | ||
* [http://dev.w3.org/csswg/css-size-adjust/ CSS Mobile Text Size Adjustment Module Level 1] | |||
== editor next actions == | |||
=== should for FPWD === | |||
==== define percentage values ==== | |||
The definition of <percentage> is not particularly clear. | |||
* Need to figure out what iOS Safari actually *does* for percentages. | |||
A somewhat reasonable guess might be that it sets a maximum inflation level, but relative to what? Is '0%' equivalent to 'none', or is '100%', or are they both different from 'none' in some way? If it actually just specifies the inflation that would be pretty bad. | |||
* Create some test cases to figure out what iOS is doing for %s and test them on an iOS device (iPhone / iPod touch / iTouch). | |||
* write-up percentage details accordingly | |||
=== should for LCWD === | |||
* resolve all issues in draft | |||
* develop a few prefixed-implementation test-cases for each value type | |||
* demonstrate interoperability of prefixed-implementation test-cases | |||
== see also == | == see also == | ||
* http://dev.w3.org/csswg/css-size-adjust/ | |||
* https://developer.mozilla.org/en/CSS/text-size-adjust | * https://developer.mozilla.org/en/CSS/text-size-adjust | ||
* http://dbaron.org/log/20111126-font-inflation | |||
* [https://developer.apple.com/library/ios/#DOCUMENTATION/AppleApplications/Reference/SafariWebContent/AdjustingtheTextSize/AdjustingtheTextSize.html -webkit-text-size-adjust] | |||
* [http://msdn.microsoft.com/en-us/library/ff462082%28v=vs.92%29.aspx#sectionToggle2 –ms-text-size-adjust] | |||
Latest revision as of 08:18, 16 September 2019
CSS text-size-adjust
This page is for tracking the development of a standard 'text-size-adjust' property. There are three known vendor prefixed implementations of it: -moz-, -ms-, -webkit-.
Web developers are using at least 4 prefixed implementations in the wild, including -o-text-size-adjust which Opera does not implement (as of 2012-088 per Florian of Opera on the CSSWG telcon that morning).
See the W3C Editor's Draft: CSS Mobile Text Size Adjustment Module Level 1
- Tantek
property definition
See the W3C Editor's Draft:
editor next actions
should for FPWD
define percentage values
The definition of <percentage> is not particularly clear.
- Need to figure out what iOS Safari actually *does* for percentages.
A somewhat reasonable guess might be that it sets a maximum inflation level, but relative to what? Is '0%' equivalent to 'none', or is '100%', or are they both different from 'none' in some way? If it actually just specifies the inflation that would be pretty bad.
- Create some test cases to figure out what iOS is doing for %s and test them on an iOS device (iPhone / iPod touch / iTouch).
- write-up percentage details accordingly
should for LCWD
- resolve all issues in draft
- develop a few prefixed-implementation test-cases for each value type
- demonstrate interoperability of prefixed-implementation test-cases