- From: Gérard Talbot <css21testsuite@gtalbot.org>
- Date: Mon, 06 Mar 2017 16:12:15 -0500
- To: Koji Ishii <kojiishi@gluesoft.co.jp>
- Cc: Public CSS Test suite mailing list <public-css-testsuite@w3.org>
Le 2016-09-24 20:12, Gérard Talbot a écrit : > Le 2016-05-31 23:58, Gérard Talbot a écrit : >> Koji, >> >> [src] >> http://test.csswg.org/source/css-writing-modes-3/page-flow-direction-002.xht >> >> [Shepherd] >> http://test.csswg.org/shepherd/testcase/page-flow-direction-002/ >> >> >> You wrote: >> " >> Could we use smaller images? On my PC with my printer, the images are >> wider than paper and each page is printed on two pages. That's not >> what we want to test here, correct? >> " >> >> I just stumbled on your comment today. The intrinsic width of the >> widest image among the 4 images is 651px. I can rearrange the images' >> intrinsic width to be narrower > > I have narrowed the 4 images so that they all are 391px wide in the > following draft and not-submitted-yet tests: > > http://www.gtalbot.org/BrowserBugsSection/CSS3WritingModes/wm-page-flow-direction-002-new.xht > > http://www.gtalbot.org/BrowserBugsSection/CSS3WritingModes/wm-page-flow-direction-003-new.xht Koji, http://www.gtalbot.org/BrowserBugsSection/CSS3WritingModes/wm-page-flow-direction-002-new.xht Dotted black line wraps <body>; dashed orange line wrap individual <div>s. Chrome 50+ fails http://www.gtalbot.org/BrowserBugsSection/CSS3WritingModes/wm-page-flow-direction-002-new.xht and http://www.gtalbot.org/BrowserBugsSection/CSS3WritingModes/wm-page-flow-direction-003-new.xht while Firefox 54.0a1 buildID=20170305110158 passes both tests. I tried adding div{page-break-inside: avoid;} to no avail. I also tried with div{page-break-after: always;} to no avail. [Addendum: Right now, I think implementations of page-break-* properties are not writing-mode-aware in Firefox and in Chrome; right now, page-break-* properties are not implemented for vertical writing-modes in Firefox and in Chrome.] The test should work *without* div{page-break-inside: avoid;} and *without* div{page-break-after: always;} because, in general, user agents, by default, try to avoid breaking, splitting blocks between pages. I think Chrome 50+ just has a writing mode implementation bug, failure with wm-page-flow-direction-002-new test, otherwise I can't see what's wrong with that test. As far as page flow (or progression) direction in page media is involved (which is the original goal/target of those tests), Chrome passes those tests. So, I could create new tests where number of printed pages would not be a factor of the pass-conditions of the tests. I could modify and convert these 2 tests for some page-break-* testing purposes. My page setup paper size is: US Letter 8.5inches wide by 11inches tall (or 215.9mm wide by 279.4mm tall). The test should also work with A4 (210mm wide by 297mm tall). I have been using Chrome 58.0.3026.3 and Chrome 56.0.2924.87. Gérard -- Test Format Guidelines http://testthewebforward.org/docs/test-format-guidelines.html Test Style Guidelines http://testthewebforward.org/docs/test-style-guidelines.html Test Templates http://testthewebforward.org/docs/test-templates.html CSS Naming Guidelines http://testthewebforward.org/docs/css-naming.html Test Review Checklist http://testthewebforward.org/docs/review-checklist.html CSS Metadata http://testthewebforward.org/docs/css-metadata.html
Received on Monday, 6 March 2017 21:12:50 UTC