Contact emails
Spec
https://www.w3.org/TR/css-page-3/#typedef-page-size-page-size
I’ve been informed that a TAG review is not needed in this case.
Explainer/Summary
The CSS Paged Media Module Level 3 spec includes a list of page size names that may be used in the "size" property of the @page rule.
Among these are two names for Japanese Industrial Standard page sizes which are currently not being recognized by Chrome:
“JIS-B5” refers to JIS B5 size (182mm wide by 257mm high)
“JIS-B4” refers to JIS B4 size (257mm wide by 364mm high)
This feature completes the implementation of this section of the standard by adding support for these two page size names.
Chromium Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1047642
CL: https://chromium-review.googlesource.com/c/chromium/src/+/2059029
Motivation
The detailed description of bug 1047642 links to some related discussions and documents. Chromium's implementation of the “size” property follows a now-obsolete version of the spec which didn't include the Japanese JIS B4 and JIS B5 paper sizes. Those were added later on following demand from Japanese users:
The B4 and B5 sizes included are very confusing for Japanese users, as they are defined as ISO B4 (250×353mm) and ISO B5 (176×250mm), different from the JIS-B4 (257×364mm) and JIS-B5 (182×257mm) commonly used in Japan. [www-...@w3c.org archives]
We need jis-b5 and jis-b4 only because (ISO) b5 and b4 are already defined and those would confuse Japanese users. [public-cs...@w3.org archives]
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes.
Risks
Interoperability and Compatibility
If support for the “size” property itself is already in place (as is the case with Chromium), adding support for the page size names listed in the spec is pretty much straightforward.
Edge: No signals
Firefox: No signals
Safari: No signals
Web / Framework developers: already defined in CSS Paged Media Module Level 3 by the CSS Working Group.
Ergonomics
This feature will have no impact on the browser's ability to maintain good performance.
Activation
No specific extra work required: these two values are already part of the spec and mentioned in online documentation sites like MDN Web Docs.
Debuggability
No extra work needed by DevTools.
Is this feature fully tested by web-platform-tests?
Not yet. I have created an issue and pull request to add those tests:
Entry on the feature dashboard
I would need somebody to create an entry for this feature, as I don’t have the necessary permissions yet.
Requesting approval to ship?
Yes.
The things you learn...
LGTM1
/Daniel
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/a8ffb1b8-836f-4fe8-aeb4-2ee4f59d5c3a%40chromium.org.
Contact emails
Spec
https://www.w3.org/TR/css-page-3/#typedef-page-size-page-size
I’ve been informed that a TAG review is not needed in this case.
Explainer/Summary
The CSS Paged Media Module Level 3 spec includes a list of page size names that may be used in the "size" property of the @page rule.
Among these are two names for Japanese Industrial Standard page sizes which are currently not being recognized by Chrome:
“JIS-B5” refers to JIS B5 size (182mm wide by 257mm high)
“JIS-B4” refers to JIS B4 size (257mm wide by 364mm high)
This feature completes the implementation of this section of the standard by adding support for these two page size names.
Chromium Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1047642
CL: https://chromium-review.googlesource.com/c/chromium/src/+/2059029
Motivation
The detailed description of bug 1047642 links to some related discussions and documents. Chromium's implementation of the “size” property follows a now-obsolete version of the spec which didn't include the Japanese JIS B4 and JIS B5 paper sizes. Those were added later on following demand from Japanese users:
The B4 and B5 sizes included are very confusing for Japanese users, as they are defined as ISO B4 (250×353mm) and ISO B5 (176×250mm), different from the JIS-B4 (257×364mm) and JIS-B5 (182×257mm) commonly used in Japan. [www-...@w3c.org archives]
We need jis-b5 and jis-b4 only because (ISO) b5 and b4 are already defined and those would confuse Japanese users. [public-cs...@w3.org archives]
Is this feature supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes.
Risks
Interoperability and Compatibility
If support for the “size” property itself is already in place (as is the case with Chromium), adding support for the page size names listed in the spec is pretty much straightforward.
Edge: No signals
Firefox: No signals
Safari: No signals
Web / Framework developers: already defined in CSS Paged Media Module Level 3 by the CSS Working Group.
Ergonomics
This feature will have no impact on the browser's ability to maintain good performance.
Activation
No specific extra work required: these two values are already part of the spec and mentioned in online documentation sites like MDN Web Docs.
Debuggability
No extra work needed by DevTools.
Is this feature fully tested by web-platform-tests?
Not yet. I have created an issue and pull request to add those tests:
Entry on the feature dashboard
I would need somebody to create an entry for this feature, as I don’t have the necessary permissions yet.
Requesting approval to ship?
Yes.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/287b9cc7-e0df-48df-9b9c-9aa165ecb377%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/a2af681b-d007-b77e-4d62-71a569765fe2%40gmail.com.
On Tue, 18 Feb 2020 at 13:36, Felipe Erias Morandeira <felip...@gmail.com> wrote:
…
I assume that the TAG review isn't needed because it's only adding new type of @page sizes and doesn't actually change anything else. Is this correct?
I don't think that the change being part of a Working Group spec is seen as a signal from Web or Framework developers. I think the intent of this question is more to check if you are aware of any web developer asking for this feature. Basically, are there strong concrete real life use cases that makes this addition useful to the platform. I think in your case, the motivation section answers this and it seems that there is a demand.Also, did you reach out to Firefox or Safari? Are there bugs open for this feature? What's the story behind it being added to the spec. Who proposed it? and why? I see that two Mozillians are editing the spec. Did you reach out to them directly maybe?
…
I've created https://chromestatus.com/feature/5112328557166592 for you.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/2df894a8-efde-4b2c-a123-9ce2f37c86d9%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2B-LeH-TpK1kz8Q3j-B24-2CX7LvHYCi2L1uurbJJpUubXTbkg%40mail.gmail.com.