CSS/text-size-adjust: Difference between revisions

From MozillaWiki
< CSS
Jump to navigation Jump to search
(link to editor's draft, note should for LCWD)
Line 4: Line 4:


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).
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]]
- [[User:Tantek|Tantek]]
Line 10: Line 12:


== property definition ==
== property definition ==
* values: auto | none | <percentage>
See the W3C Editor's Draft:  
* Initial value : auto for smartphone browsers supporting inflation, none in other cases (and then not modifiable)
* [http://dev.w3.org/csswg/css-size-adjust/ CSS Mobile Text Size Adjustment Module Level 1]
* Applies to: all elements
* Inherited :yes
* <percentage> :yes, refer to the corresponding size of the text font
* Media: visual
* Computed value : the keyword or the percentage value
* Animatable: no
 
;auto
: mobile browsers may implement a text inflation algorithm
;none
: browser must not do any automatic text inflation
;<percentage>
: inflate text size by the <percentage> given
 
Text inflation ... (needs to be defined).


== editor next actions ==
== editor next actions ==
=== must for editor draft ===
* define text inflation (as requested by CSSWG 2012-088 telcon before checking in as editor's draft)
=== should for FPWD ===
=== should for FPWD ===
==== define percentage values ====
==== define percentage values ====
Line 41: Line 26:
* Create some test cases to figure out what iOS is doing for %s and test them on an iOS device (iPhone / iPod touch / iTouch).
* 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
* 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
* http://dbaron.org/log/20111126-font-inflation
* [https://developer.apple.com/library/ios/#DOCUMENTATION/AppleApplications/Reference/SafariWebContent/AdjustingtheTextSize/AdjustingtheTextSize.html -webkit-text-size-adjust]
* [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]
* [http://msdn.microsoft.com/en-us/library/ff462082%28v=vs.92%29.aspx#sectionToggle2 –ms-text-size-adjust]

Revision as of 20:49, 27 April 2012

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

see also