Intent to implement & ship: CSS font-synthesis-position property
75 views
Skip to first unread message
Jonathan Kew
Aug 17, 2023, 12:06:15 PM8/17/23
to dev-pl...@mozilla.org
As of Firefox 118, I intend to implement the CSS property
'font-synthesis-position'.
This property allows authors to control whether synthetic ("fake")
super- and sub-script characters should be rendered for the
'font-variant-position' property, if the font being used does not
support these alternate forms directly.
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1849010
Standard: To be added to CSS Fonts; see
https://drafts.csswg.org/css-fonts-4/#font-synthesis-intro for the
existing 'font-synthesis-*' properties and 'font-synthesis' shorthand,
and
https://github.com/w3c/csswg-drafts/issues/7441#issuecomment-1680918811
for the resolution to add this subproperty.
Testing: New WPT tests included with the patch.
Other browsers: Not yet implemented, though at least Blink seems
actively interested.
Platform coverage: All
Restricted to secure contexts: No; this is an extension to existing
universally-available CSS properties
Target Release: 118
Preferences behind which this will be implemented: none
'font-synthesis-position'.
This property allows authors to control whether synthetic ("fake")
super- and sub-script characters should be rendered for the
'font-variant-position' property, if the font being used does not
support these alternate forms directly.
Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1849010
Standard: To be added to CSS Fonts; see
https://drafts.csswg.org/css-fonts-4/#font-synthesis-intro for the
existing 'font-synthesis-*' properties and 'font-synthesis' shorthand,
and
https://github.com/w3c/csswg-drafts/issues/7441#issuecomment-1680918811
for the resolution to add this subproperty.
Testing: New WPT tests included with the patch.
Other browsers: Not yet implemented, though at least Blink seems
actively interested.
Platform coverage: All
Restricted to secure contexts: No; this is an extension to existing
universally-available CSS properties
Target Release: 118
Preferences behind which this will be implemented: none
Martin Thomson
Aug 17, 2023, 12:29:45 PM8/17/23
to Jonathan Kew, dev-pl...@mozilla.org
It looks like the specification for this is https://github.com/w3c/csswg-drafts/issues/7441#issuecomment-1444461111 plus an amendment to make 'auto' mean that synthesis is mandatory rather than simply allowed.
Though the record shows this as an agreed plan and it seems uncomplicated, it would be good to make shipping conditional on the agreed change being complete. I've seen enough cases where working through the details -- in either implementation or specification -- uncovered unpleasant surprises.
--
You received this message because you are subscribed to the Google Groups "dev-pl...@mozilla.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dev-platform...@mozilla.org.
To view this discussion on the web visit https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/bb4241f8-3009-b9b2-4ec2-0ad01e671ce2%40gmail.com.
Jonathan Kew
Aug 17, 2023, 12:52:27 PM8/17/23
to Martin Thomson, dev-pl...@mozilla.org
On 17/08/2023 13:29, Martin Thomson wrote:
> It looks like the specification for this is
> https://github.com/w3c/csswg-drafts/issues/7441#issuecomment-1444461111
> <https://github.com/w3c/csswg-drafts/issues/7441#issuecomment-1444461111> plus an amendment to make 'auto' mean that synthesis is mandatory rather than simply allowed.
>
> Though the record shows this as an agreed plan and it seems
> uncomplicated, it would be good to make shipping conditional on the
> agreed change being complete. I've seen enough cases where working
> through the details -- in either implementation or specification --
> uncovered unpleasant surprises.
Fair point; I'll see if we can get the spec edits completed promptly.
> It looks like the specification for this is
> https://github.com/w3c/csswg-drafts/issues/7441#issuecomment-1444461111
> <https://github.com/w3c/csswg-drafts/issues/7441#issuecomment-1444461111> plus an amendment to make 'auto' mean that synthesis is mandatory rather than simply allowed.
>
> Though the record shows this as an agreed plan and it seems
> uncomplicated, it would be good to make shipping conditional on the
> agreed change being complete. I've seen enough cases where working
> through the details -- in either implementation or specification --
> uncovered unpleasant surprises.
(Regarding implementation surprises, there's a patch with tests already
in hand, so not too worried about that.)
JK
>
> On Thu, Aug 17, 2023 at 8:06 AM Jonathan Kew <jfkt...@gmail.com
> <mailto:jfkt...@gmail.com>> wrote:
>
> As of Firefox 118, I intend to implement the CSS property
> 'font-synthesis-position'.
>
> This property allows authors to control whether synthetic ("fake")
> super- and sub-script characters should be rendered for the
> 'font-variant-position' property, if the font being used does not
> support these alternate forms directly.
>
> Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1849010
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1849010>
>
> Standard: To be added to CSS Fonts; see
> https://drafts.csswg.org/css-fonts-4/#font-synthesis-intro
> <https://drafts.csswg.org/css-fonts-4/#font-synthesis-intro> for the
> existing 'font-synthesis-*' properties and 'font-synthesis' shorthand,
> and
> for the resolution to add this subproperty.
>
> Testing: New WPT tests included with the patch.
>
> Other browsers: Not yet implemented, though at least Blink seems
> actively interested.
>
> Platform coverage: All
>
> Restricted to secure contexts: No; this is an extension to existing
> universally-available CSS properties
>
> Target Release: 118
>
> Preferences behind which this will be implemented: none
>
> --
> You received this message because you are subscribed to the Google
> Groups "dev-pl...@mozilla.org <mailto:dev-pl...@mozilla.org>"
>
> Testing: New WPT tests included with the patch.
>
> Other browsers: Not yet implemented, though at least Blink seems
> actively interested.
>
> Platform coverage: All
>
> Restricted to secure contexts: No; this is an extension to existing
> universally-available CSS properties
>
> Target Release: 118
>
> Preferences behind which this will be implemented: none
>
> --
> You received this message because you are subscribed to the Google
> group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to dev-platform...@mozilla.org
> <mailto:dev-platform%2Bunsu...@mozilla.org>.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to dev-platform...@mozilla.org
> To view this discussion on the web visit
> https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/bb4241f8-3009-b9b2-4ec2-0ad01e671ce2%40gmail.com <https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/bb4241f8-3009-b9b2-4ec2-0ad01e671ce2%40gmail.com>.
>
Jonathan Kew
Aug 28, 2023, 9:14:08 PM8/28/23
to Martin Thomson, dev-pl...@mozilla.org
On 17/08/2023 08:29, Martin Thomson wrote:
> It looks like the specification for this is
> https://github.com/w3c/csswg-drafts/issues/7441#issuecomment-1444461111
> <https://github.com/w3c/csswg-drafts/issues/7441#issuecomment-1444461111> plus an amendment to make 'auto' mean that synthesis is mandatory rather than simply allowed.
>
> Though the record shows this as an agreed plan and it seems
> uncomplicated, it would be good to make shipping conditional on the
> agreed change being complete. I've seen enough cases where working
> through the details -- in either implementation or specification --
> uncovered unpleasant surprises.
>
Just to follow up on this: the spec has now been updated to include this
> It looks like the specification for this is
> https://github.com/w3c/csswg-drafts/issues/7441#issuecomment-1444461111
> <https://github.com/w3c/csswg-drafts/issues/7441#issuecomment-1444461111> plus an amendment to make 'auto' mean that synthesis is mandatory rather than simply allowed.
>
> Though the record shows this as an agreed plan and it seems
> uncomplicated, it would be good to make shipping conditional on the
> agreed change being complete. I've seen enough cases where working
> through the details -- in either implementation or specification --
> uncovered unpleasant surprises.
>
property:
https://drafts.csswg.org/css-fonts-4/#font-synthesis-position
and there are basic WPT tests in place:
https://wpt.fyi/results/css/css-fonts?label=master&label=experimental&aligned&q=font-synthesis-
https://wpt.fyi/results/css/css-fonts?label=master&label=experimental&aligned&q=font-variant-position-0
> On Thu, Aug 17, 2023 at 8:06 AM Jonathan Kew <jfkt...@gmail.com
> <mailto:jfkt...@gmail.com>> wrote:
>
> As of Firefox 118, I intend to implement the CSS property
> 'font-synthesis-position'.
>
> This property allows authors to control whether synthetic ("fake")
> super- and sub-script characters should be rendered for the
> 'font-variant-position' property, if the font being used does not
> support these alternate forms directly.
>
> Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1849010
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1849010>
>
> Standard: To be added to CSS Fonts; see
> https://drafts.csswg.org/css-fonts-4/#font-synthesis-intro
> <https://drafts.csswg.org/css-fonts-4/#font-synthesis-intro> for the
> existing 'font-synthesis-*' properties and 'font-synthesis' shorthand,
> and
> for the resolution to add this subproperty.
>
> Testing: New WPT tests included with the patch.
>
> Other browsers: Not yet implemented, though at least Blink seems
> actively interested.
>
> Platform coverage: All
>
> Restricted to secure contexts: No; this is an extension to existing
> universally-available CSS properties
>
> Target Release: 118
>
> Preferences behind which this will be implemented: none
>
> --
> You received this message because you are subscribed to the Google
> Groups "dev-pl...@mozilla.org <mailto:dev-pl...@mozilla.org>"
>
> Testing: New WPT tests included with the patch.
>
> Other browsers: Not yet implemented, though at least Blink seems
> actively interested.
>
> Platform coverage: All
>
> Restricted to secure contexts: No; this is an extension to existing
> universally-available CSS properties
>
> Target Release: 118
>
> Preferences behind which this will be implemented: none
>
> --
> You received this message because you are subscribed to the Google
> group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to dev-platform...@mozilla.org
> <mailto:dev-platform%2Bunsu...@mozilla.org>.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to dev-platform...@mozilla.org
> To view this discussion on the web visit
> https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/bb4241f8-3009-b9b2-4ec2-0ad01e671ce2%40gmail.com <https://groups.google.com/a/mozilla.org/d/msgid/dev-platform/bb4241f8-3009-b9b2-4ec2-0ad01e671ce2%40gmail.com>.
>
Reply all
Reply to author
Forward
0 new messages