- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Mar 2020 00:42:27 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-page-3] Add orientation descriptor`, and agreed to the following: * `RESOLVED: Name this page-orientation with values rotate-left and rotate-right` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-page-3] Add orientation descriptor<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/4491<br> <dael> chrishtr: Discussed in Dec. Can add to a named page to control rotation in printed output.<br> <dael> chrishtr: Use cases are to provide orientation for dominant content direction when multi direction. Second it allow dev to provide mixed rotations for UA that don't support other page rotation parts<br> <dael> chrishtr: I think some consensus use cases make sense.<br> <dael> chrishtr: Discussion on name<br> <dael> chrishtr: Check for consensus and then do name<br> <fantasai> https://github.com/w3c/csswg-drafts/issues/4491#issuecomment-590613842<br> <dael> fantasai: Not clear on the behavior of this. I read TabAtkins comment that makes sense but you said it's not that<br> <dael> TabAtkins: What happens is in cases where printed output but you control how pages are displaded, aka pdf, adjusts how they're oriented in that display.<br> <dael> TabAtkins: You can have a whole bunch of portrait and then some are landscape<br> <dael> fantasai: Example in comment. Doc with a table, assign table to landscape with features we have. Printer the landscape is oriented to portrait. When open a PDF you get a bunch of portrait pages and a landscape for the page that has a table which is upright for me on the screen. THat's without this property. Current behavior<br> <bkardell_> https://docs.google.com/document/d/1plEqcBz_6ApmtWYCSRxwOANgF5aGoAL2B0s_9PSQJF0/edit#heading=h.zd7icrtuskjo<br> <dael> fantasai: Prop is to rotate the landscape so it's sidewas and you have to turn your head to read?<br> <dael> TabAtkins: It's something else<br> <dael> fantasai: What is the default that should happen right now?<br> <dael> TabAtkins: Ideally you do what you desc. Wide table you force to a named page and say landscape<br> <dael> TabAtkins: In scenario today where browsers do not have ability to do diff size page sin layout what you instead do is layout everything as portrait. If that means putting out bitmaps or whatever it all comes out as portrait.<br> <dael> TabAtkins: This feature then says if you're output to a pdf go ahead and rotate. This is a the good feature isn't impl so let's put in this feature for now. It'll be a few years before browser can address properly<br> <dael> fantasai: Okay, I think I understand. So this rotates whole paper including headers<br> <dael> TabAtkins: Correct.<br> <bkardell_> q+<br> <dael> TabAtkins: When browser can control paper orientation is this property<br> <astearns> ack bkardell_<br> <dael> fantasai: Use case you're bringing up is you pre-rotate and then rotate back to get effect of if we had portrait/landscape<br> <dael> TabAtkins: Correct<br> <dael> bkardell_: I shared a google doc from gsuites that talked about uses involving mixed orientations. Is that included here?<br> <dael> chrishtr: mixed means some landscape and some portrait. Use case from TabAtkins is a browser that doesn't fully support to still be able to output.<br> <dael> bkardell_: I see that in issue. THanks<br> <fantasai> s/Use case/So your original comment is correct, and the additional use case/<br> <fantasai> s/pre-rotate/pre-rotate using writing-mode or transform or something/<br> <dael> astearns: Currently for output formats that can handle layout orientation. When browser can layout as a landscape page owuld this property start applying to on screen?<br> <dael> fantasai: No<br> <dael> TabAtkins: Not unless display in paged format which generally don't<br> <dael> chrishtr: If site applies page:landscape and rotate:left you get things that look sideways. Shouldn't do that. SHould only apply rotate for layout of printed mode<br> <dael> astearns: I'm thinking of paged view on tablet. Currently...if you had this you could layout such that someone can rotate screen and get better view of horz content<br> <dael> chrishtr: Cases where drown by dev layout but paginated layout?<br> <dael> astearns: Future browser with paginated ux<br> <dael> TabAtkins: Got it. Depends on if it allows rotation of pages. If wants to be more like printed it would not respect. BUt if it's just layout onto desktop screen it would respect this property and rotate the page for you<br> <dael> chrishtr: If you consider pdf viewer on tablet you can imagine browser to integrate with pdf viewer to not respect this and expect you to rotate. It's an option impl could choose<br> <dael> fantasai: It's a good point astearns and we should write up that situation<br> <dael> astearns: I've got people with defined opinions on pdf viewers we can consult<br> <dael> TabAtkins: Want to make sure it's clear in description where this applies. Paginated viewing and makes sense to author oritentation of page based on user preference not device orientation. Happy to work together to make sure text looks good<br> <dael> astearns: Other questions or opinions on basic design before we do naming?<br> <dael> astearns: Let's talk names<br> <dael> astearns: My opinion is page-rotate makes sense since talking pagination<br> <dael> chrishtr: Makes sense to me<br> <dael> astearns: Other opinions?<br> <dael> astearns: We're not setting anything in stone. I think for now go with page-rotate and with issue discussion<br> <dael> fantasai: page-rotate or page-orient. rotate left and right makes sense<br> <dael> TabAtkins: I like rotate because it's spinning. I would accept orientation<br> <dael> fantasai: I think that was my opinion until PDF cases where this is a hint about correct orientation but you might not honor that. It's hint about orientation but not a command to rotate. I'm not super clear<br> <dael> astearns: In order to prevent a verb should it be page-rotation?<br> <fantasai> s/PDF cases/astearn's examples,/<br> <dael> astearns: Seems like we're at a lull. Should we resolve on name page-rotation?<br> <dael> fantasai: Have rotate property<br> <dael> TabAtkins: But it's a rotate function. There's a reason for it to be a verb when we normally have adjectives<br> <dael> fantasai: I feel inconsistency is not great<br> <dael> dholbert: Rotate sounds like an angle rather then keyword<br> <dael> TabAtkins: Breaking with rotate is good<br> <dael> TabAtkins: Page-oreitnetation<br> <dael> chris: People talk about page orientation<br> <dael> chris: page-orientation rotate-left and rotate-right?<br> <dael> astearns: Makes sense. Rotate seems angle<br> <dael> astearns: page-orientation with values rotate-left and rotate-right<br> <dael> dholbert: Don't love rotate-left b/c sounds like clockwise and counter clockwise. Left is direction rather then rotation. It's translation<br> <dael> chrishtr: left is 90deg rather then rotate<br> <dael> dholbert: Suggests counterclockwise<br> <dael> astearns: And easier to spell<br> <dael> astearns: Other concerns?<br> <dael> astearns: Objections?<br> <dael> RESOLVED: Name this page-orientation with values rotate-left and rotate-right<br> <dael> astearns: Anything else you wanted on this chrishtr ?<br> <dael> chrishtr: That's it, thank you<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4491#issuecomment-594967467 using your GitHub account
Received on Thursday, 5 March 2020 00:42:30 UTC