CARVIEW |
Select Language
HTTP/2 200
date: Mon, 06 Oct 2025 05:48:26 GMT
content-type: text/html
content-encoding: gzip
last-modified: Sat, 15 Jul 2023 03:17:11 GMT
cache-control: max-age=2592000, public
expires: Wed, 05 Nov 2025 05:48:25 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98a2dea1f9207679
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: MISS
set-cookie: __cf_bm=NPK0diBAXC3BaZHXv9sA9QKj2F2bVrR_QFbqE.I2lDQ-1759729706-1.0.1.1-HsVm.J_fcSejhcpLo_oJNAC6fTbdc9x9qHjD4c0R.SJlJOrsC9kpg8sr_8BxK1A11gGe2FoJuCqMw8I1SohLMzl2rerS6vKcdA_oGfOIDbM; path=/; expires=Mon, 06-Oct-25 06:18:26 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98a2dea1f9207679-BLR
alt-svc: h3=":443"; ma=86400
Re: [CSSWG] Minutes Telecon 2014-12-10 from Tab Atkins Jr. on 2014-12-11 (www-style@w3.org from December 2014)
Re: [CSSWG] Minutes Telecon 2014-12-10
- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 11 Dec 2014 11:15:54 -0800
- To: Dael Jackson <daelcss@gmail.com>
- Cc: www-style list <www-style@w3.org>
- Message-ID: <CAAWBYDC7mhAOyhVju1b=mZw_VTf8tqibN6hEM9P+8_u6SOuJ2A@mail.gmail.com>
The bridge being full kept me from really being in the call, and I didn't follow along well on IRC, so I have a few things I'd like to object to. On Thu, Dec 11, 2014 at 7:33 AM, Dael Jackson <daelcss@gmail.com> wrote: > - RESOLVED: Keep allowing *-identifier when it's not digits and > recommend a string when it is. I think we should simplify this, and *only* allow ident or string. This means that *-foo would no longer be allowed, as it's a delim followed by an ident. The current resolution invites confusion when people use a reasonable-looking :lang(*-foo) in one spot and it works, but :lang(*-2000) somewhere else doesn't. (Plus the also-mentioned issue that :lang(*-foo) works, but :lang(foo-*-bar) doesn't, despite the latter being a valid wildcard tag per the RFC.) CSS's parsing rules shouldn't be exposed to authors unless necessary. It would be better to require authors to use a string if they want to use asterisks, as that works in all cases. (If they're masochistic they could escape the asterisk to make the whole thing a single ident, and that's fine; we don't need to actually worry about that.) > - RESOLVED: Implementors may directly manipulate width and height > elements on the style attr being changed and change "resize > factor" to "resize function" to address fantasai's concern > (issues 47 and 53) I object to keeping the optional hidden resize factor. Nobody does it, and to the best of my knowledge nobody plans to; I wouldn't be surprised if there is code depending on resize causing explicit style attribute changes. We should just spec the actual interoperable behavior and require that, rather than maintaining the polite fiction of an imagined better world. ~TJ
Received on Thursday, 11 December 2014 19:16:43 UTC