- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Oct 2018 16:17:06 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``Add value `horizontal-text` to property `cursor` ``. <details><summary>The full IRC log of that discussion</summary> <dael> Topic: Add value `horizontal-text` to property `cursor`<br> <dael> github: github: https://github.com/w3c/csswg-drafts/issues/3196#issuecomment-427739133<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/3196#issuecomment-427739133<br> <dael> florian: Conversation has evolved. THe property has 2 values about text: text and vertical-text. text is a vertical I beam that usually shows like it's horizontal, but the browser may show vertical at vertical and may do angles. That we have one must on vertical but a may on text it's a problem.<br> <dael> florian: Suggestion is change the may to a must. If it's over vertical you must match. Diagonal I think stays as a should.<br> <dael> florian: If we get that for text we can deprecate vertical-text<br> <dael> dbaron: State of implementations switching to vertical?<br> <dael> florian: I don't remember. At least one impl does it, but I don't remember if more than one<br> <dael> astearns: I'd be more happy to resolve if we have an impl report<br> <dael> astearns: If this is something we'd have to wait on bugs or if this is uncontroversial<br> <dael> florian: It is not something everyone impl.<br> <dael> florian: I think I have the list, but I'd have to find it.<br> <dael> myles: Webkit does rotate<br> <heycam> Gecko also does<br> <dael> dbaron: I can tell you Gecko has code that does it, though I haven't made sure it works<br> <dael> florian: Test harness is tto slow to pull results<br> <dael> dbaron: It's possible we only work for auto<br> <dael> fantasai: Works for text.<br> <dael> myles: Chrome, FF and Webkit all rotate<br> <dael> florian: So shouldn't have too many problems with must<br> <dbaron> I'd note the test should test behavior both with 'cursor: auto' and with 'cursor: text'<br> <dael> florian: I will not current phrasing does not care if the text is vertical due to a specific reason. not sure we've tested all those variants<br> <dbaron> and the Gecko code only looks at writing mode<br> <dael> astearns: Suggestion is change the wording that it's must when writing mode gives you vertical?<br> <fantasai> Gecko doesn't look at transforms<br> <dael> florian: At least writin modes. If we can do any reason it's nice. Angled cursor except 0 or 90 deg should be a should<br> <dael> florian: For 90deg transforms what do people think?<br> <fantasai> Neither does Chrome<br> <dael> gregwhitworth: WIth transforms we don't change ours. I would struggle to feel that is a high priority for webdevs. For vertical it makes sense. I think that's where I would start and then try and find a common pattern<br> <dael> florian: So must on writing mode, should on transforms<br> <dael> fantasai: Yeah<br> <dael> myles: If no impl I'm not sure it should be a should<br> <dael> florian: Keep as a may?<br> <dael> gregwhitworth: May sounds right. Majority of webdevs aren't using text you'd want copy/paste at odd angles. I'd put may. If someone wants that step sure.<br> <dael> florian: So that's unchanged, make it a must for vertical writing modes<br> <dael> astearns: Prop: Change cursor in vertical writing mode to a must<br> <dael> astearns: Obj?<br> <dael> resolved: Change cursor in vertical writing mode to a must<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3196#issuecomment-430693269 using your GitHub account
Received on Wednesday, 17 October 2018 16:17:08 UTC