- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Mon, 09 Apr 2018 08:38:26 +0000
- To: public-houdini-archive@w3.org
The Working Group just discussed `Loading and absolutization timing`, and agreed to the following resolutions: * `RESOLVED: We accept this proposal https://github.com/w3c/css-houdini-drafts/issues/716#issuecomment-368659261 but also expose the original URL and base URL` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: Loading and absolutization timing<br> <dael> TabAtkins: CSS is currenlty vague. It happens at some point but we don't know when.<br> <dael> github: https://github.com/w3c/css-houdini-drafts/issues/716<br> <nainar> https://github.com/w3c/css-houdini-drafts/issues/716#issuecomment-368659261<br> <dael> TabAtkins: Her'es my proposal ^<br> <dael> TabAtkins: Has a URL attribute. It's either an absolute or a bare hash. If it's not a bare hash we'll use CSS ruels. Underlying value may not be absolutized, but when it reifies we turn it absolute. If you move a style from one doc to another it may be relative in the old way, but it's now absolute.<br> <dael> TabAtkins: I think that's what people want.<br> <dael> TabAtkins: When you contruct a value it's absolutized immediately.<br> <dael> dbaron: When is it bare hash?<br> <dael> TabAtkins: When you pass it in as a local reference.<br> <dael> TabAtkins: That's spec in the value spec?<br> <dael> plinss: It's a string not a URL?<br> <dael> TabAtkins: Yes, it's strictly spec that it's a string.<br> <dael> TabAtkins: Only controversy is the early absolutizing. Is that okay or shouldwe make it retain it's relativeness and better define when it stops being relative.<br> <dael> TabAtkins: If you want to manipulate the URL the URL spec requires an absolute value or a URL with a base. It would be harder for authors since it's hard to get the base.<br> <dael> plinss: Would it make sense to keep it as a relative URL but also expose it as a base?<br> <dael> TabAtkins: Possibly. In the current CSS if you use the OM APIs if you pull a reltivate URL and write it somewhere else it changes the base.<br> <dael> plinss: Are we allowing authors to rationalize it as a valid URL if they want to.<br> <dael> TabAtkins: Do authors want this?<br> <dael> plinss: Yes<br> <dael> TabAtkins: I doubt they do. When this occurs style sheets are usually in same folder.<br> <dael> nainar: If we're being more eager about absolutizing should that be in css as well?<br> <dael> TabAtkins: Pos.<br> <dael> birlets: I'm wondering if there's a cloning use case?<br> <dael> TabAtkins: But would people want to do that?<br> <dael> TabAtkins: I can come up with a reason, but it's a minority case.<br> <dael> krit: If you provide the bbase would you still get back relative?<br> <dael> TabAtkins: You have to know where the split happened. If impl want to preserve I can attach the original URL. But the core easiest to use should be absolute.<br> <dael> krit: I'm fine with it as a default.<br> <dael> plinss: I expect there will be use cases, like editor. In my experience any time someone tries to help me with URL they get in the way at some point. If it's distructive that's painful. If there's a way to preserve the original url.<br> <dael> dbaron: Seems like it's not crazy to have multi accessors.<br> <dael> TabAtkins: I'm happy to put on an original URL value.<br> <dbaron> s/multi/multiple/<br> <dael> plinss: Should that but the URL<br> <dael> TabAtkins: All the DOM apis do absolute URLs.<br> <dael> TabAtkins: Prop: We accept this proposal but also expose the original URL.<br> <dael> dbaron: You could also expose base URL<br> <nainar> Proposal is comment in https://github.com/w3c/css-houdini-drafts/issues/716#issuecomment-368659261<br> <dael> TabAtkins: That would have to be dynamic. Oh, base URL as this instant. I could do that.<br> <dael> dbaron: I don't know how useful, but if you're exposing a bunch of information.<br> <dael> Rossen_: Okay.<br> <dael> Rossen_: Suggestions, objections?<br> <dael> RESOLVED: We accept this proposal https://github.com/w3c/css-houdini-drafts/issues/716#issuecomment-368659261 but also expose the original URL and base URL<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/716#issuecomment-379677603 using your GitHub account
Received on Monday, 9 April 2018 08:38:28 UTC