On Fri, Jun 27, 2014 at 2:00 AM, Justin Novosad wrote:
> Hadn't thought of that. object-fit seems smells dangerous. I think we may
> need to define explicit behaviors for renderedPixelWidth/Height for the
> different object fit modes.
I don't think so. Given renderedPixelWidth/Height returns th
On Thu, Jun 26, 2014 at 1:40 PM, Anne van Kesteren wrote:
> On Thu, Jun 26, 2014 at 10:32 PM, Tab Atkins Jr. wrote:
>> The spec does not suggest that it would be a simple color; it says to
>> allow any CSS color. "simple color" in HTML is solely a 6-digit hex
>> color.
>
> In that case you want
On 26 Jun 2014, at 22:37, Tab Atkins Jr. wrote:
> On Thu, Jun 26, 2014 at 1:33 PM, Mathias Bynens wrote:
>> On 26 Jun 2014, at 22:24, Mathias Bynens wrote:
>>
>>> Interesting to see this would be only the second HTML attribute value to
>>> get parsed as a simple color
>>> (http://www.whatwg.
On Thu, Jun 26, 2014 at 10:32 PM, Tab Atkins Jr. wrote:
> The spec does not suggest that it would be a simple color; it says to
> allow any CSS color. "simple color" in HTML is solely a 6-digit hex
> color.
In that case you want the same code path uses. As well as
setting some kind of initial c
On Thu, Jun 26, 2014 at 1:33 PM, Mathias Bynens wrote:
> On 26 Jun 2014, at 22:24, Mathias Bynens wrote:
>
>> Interesting to see this would be only the second HTML attribute value to get
>> parsed as a simple color
>> (http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsynt
On Thu, Jun 26, 2014 at 1:24 PM, Mathias Bynens wrote:
> Interesting to see this would be only the second HTML attribute value to get
> parsed as a simple color
> (http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#simple-color)
> rather than a legacy color (t
On 26 Jun 2014, at 22:24, Mathias Bynens wrote:
> Interesting to see this would be only the second HTML attribute value to get
> parsed as a simple color
> (http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#simple-color)
> rather than a legacy color (the oth
On 26 Jun 2014, at 20:45, Domenic Denicola wrote:
> I would like to reiterate that "brand-" is not a good prefix for this
> purpose. It has nothing to do with brands, and much more to do with the app
> or with system integration.
Major +1 here, seeing as this feedback was ignored before. Just
> http://meiert.com/en/indices/html-elements/
Based on feedback from people on this list and public-html, the index
now includes what appears to be the first version of HTML, irons out
an inconsistency with respect to Strict and Transitional document
types, and features a tiny bit more info.
I re
On June 26, 2014 at 2:17:22 PM, Ian Hickson (i...@hixie.ch) wrote:
> > I think it would make sense to allow vendors to treat these all
> as
> independent values (in particular, we wouldn't want IE to be
> forced to
> extend their interpretation of "msapplication-TileColor"
> and
> "msapplica
2557-06-27 2:08 GMT+07:00, whatwg-requ...@lists.whatwg.org
:
> Send whatwg mailing list submissions to
> whatwg@lists.whatwg.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.whatwg.org/listinfo.cgi/whatwg-whatwg.org
> or, via email, send a message with su
On Jun 26, 2014, at 21:20, Marcos Caceres wrote:
> On June 26, 2014 at 1:58:17 PM, Tab Atkins Jr. (jackalm...@gmail.com) wrote:
>>> Here's a first crack at a better spec:
>
> Moved your text here:
>
> https://github.com/whatwg/meta-brand-color
Could we change the name to something a tad more neu
On Thu, Jun 26, 2014 at 12:09 PM, Boris Zbarsky wrote:
> On 6/26/14, 2:57 PM, Тимофей Маринин wrote:
>>
>> Do you mean "if style src were supported"?
>
> No, I mean what I said. But looks like
On June 26, 2014 at 1:58:17 PM, Tab Atkins Jr. (jackalm...@gmail.com) wrote:
> > Here's a first crack at a better spec:
Moved your text here:
https://github.com/whatwg/meta-brand-color
We can better capture issues, etc. there. I also updated the Wiki to point
there as the "official" version.
On 6/26/14, 2:57 PM, Тимофей Маринин wrote:
Do you mean "if style src were supported"?
No, I mean what I said. But looks like
+1 to either much more than
Отправлено с iPhone
> 26 июня 2014 г., в 19:31, Boris Zbarsky написал(а):
>
>> On 6/26/14, 10:39 AM, Tim Marinin wrote:
>> If not, then why we need for css, only for legacy reasons?
>
> Pretty much, yes. If
I would like to reiterate that "brand-" is not a good prefix for this purpose.
It has nothing to do with brands, and much more to do with the app or with
system integration.
On Thu, Jun 26, 2014 at 11:13 AM, Ian Hickson wrote:
> On Thu, 26 Jun 2014, Tao Bai wrote:
>> The brand color is super set of them and not limited to use in the
>> navbutton or status bar, furthermore, not all browsers have navbutton or
>> status concept, it makes developer confused.
>
> I don't t
JavaScripture.com a bridge between W3C && EMCAScript.
Please take a look, this site make it easy to navigate in W3C and EMCAScript.
The only thing it's missing is WHATWG!
On Thu, 26 Jun 2014, Tab Atkins Jr. wrote:
> On Thu, Jun 26, 2014 at 10:57 AM, Tab Atkins Jr. wrote:
> > This feature has been developed in the past under multiple proprietary
> > names, such as "mapplication-navbutton-color" for Internet Explorer
> > and "apple-mobile-web-app-status-bar-style" fo
On Thu, 26 Jun 2014, Anne van Kesteren wrote:
> On Thu, Jun 26, 2014 at 7:36 PM, L2L 2L wrote:
> > Could/is there [be] a mailing list that send out information on new updates
> > on HTML tags, etc. and more?
>
> There's https://twitter.com/whatwg
>
> There's also a ton of GitHub repositories yo
On Thu, 26 Jun 2014, Tao Bai wrote:
>
> The brand color is super set of them and not limited to use in the
> navbutton or status bar, furthermore, not all browsers have navbutton or
> status concept, it makes developer confused.
I don't think it confuses authors any more, and possibly a lot less
On Thu, Jun 26, 2014 at 10:40 AM, Chris Lilley wrote:
>> Better integration of HTML and SVG (and blocking any further
>> element copying beyond the four existing elements) is really
>> important.
>
> Much more important than maintaining rendering of someone's "tried this
> and it didn't do anythi
On Thu, Jun 26, 2014 at 10:57 AM, Tab Atkins Jr. wrote:
> This feature has been developed in the past under multiple proprietary
> names, such as "mapplication-navbutton-color" for Internet Explorer
> and "apple-mobile-web-app-status-bar-style" for Mobile Safari.
> Authors MUST NOT use the proprie
On 06/26/2014 01:18 AM, Mikko Rantalainen wrote:
> However, the suggested hash signature is far from enough. Most popular
> libraries have means to load additional files and plugins and the
> suggested hash is able to "sign" only the main file. If you cannot
> trust the CDN provider, you cannot tr
On Thu, Jun 26, 2014 at 10:35 AM, Marcos Caceres wrote:
> Folks at Mozilla and Google would like to standardize the `brand-color` meta
> extension. The `brand-color` keyword has been added to the MetaExtensions
> WHATWG wiki and a rough spec is below (prepared by some folks at Google).
>
> # Ove
The brand color is super set of them and not limited to use in the
navbutton or status bar, furthermore, not all browsers have navbutton or
status concept, it makes developer confused.
The "mapplication-navbutton-color"
and "apple-mobile-web-app-status-bar-style" are prefix and browser
specific, br
On Thu, Jun 26, 2014 at 7:36 PM, L2L 2L wrote:
> Could/is there [be] a mailing list that send out information on new updates
> on HTML tags, etc. and more?
There's https://twitter.com/whatwg
There's also a ton of GitHub repositories you can watch:
https://github.com/whatwg/ (some also have an a
Could/is there [be] a mailing list that send out information on new updates on
HTML tags, etc. and more?
Please tell!
Folks at Mozilla and Google would like to standardize the `brand-color` meta
extension. The `brand-color` keyword has been added to the MetaExtensions
WHATWG wiki and a rough spec is below (prepared by some folks at Google).
# Overview
The browser will use this brand color when distinct color
On Thu, 26 Jun 2014, Tao Bai wrote:
>
> Hi, I have added brand-color meta extension in
> http://wiki.whatwg.org/wiki/MetaExtensions, and would like have your
> comment on it. Please check the detail on linked spec.
The cited spec mentions "mapplication-navbutton-color" and
"apple-mobile-web-app
On Thu, Jun 26, 2014 at 6:48 PM, Tab Atkins Jr. wrote:
> How many of these crazy sites were there? I'd hate to flounder on such
> an important change due to just a handful of idiotically-authored
> sites. Better integration of HTML and SVG (and blocking any further
> element copying beyond the fo
Hi, I have added brand-color meta extension in
http://wiki.whatwg.org/wiki/MetaExtensions,
and would like have your comment on it. Please check the detail on linked
spec.
Best Regards
- Michael
On Thu, Jun 26, 2014 at 9:44 AM, Anne van Kesteren wrote:
> On Thu, Jun 26, 2014 at 6:35 PM, Tab Atkins Jr. wrote:
>> (The current proposal would place all the direct HTML children of SVG
>> elements on top of each other, similar to abspos, but grandchildren
>> would render normally, in a CSS lay
On Thu, Jun 26, 2014 at 6:35 PM, Tab Atkins Jr. wrote:
> (The current proposal would place all the direct HTML children of SVG
> elements on top of each other, similar to abspos, but grandchildren
> would render normally, in a CSS layout model.)
Isn't content outside of clipped though?
--
htt
On Thu, Jun 26, 2014 at 9:11 AM, Ian Hickson wrote:
> On Tue, 24 Jun 2014, Robert O'Callahan wrote:
>>
>>
>>
>>
>>
>> the elements "s" and "i" are put in the HTML namespace already.
>
> As siblings of the element, though, not descendants.
>
> This was required to get some level of compatibili
On Tue, 24 Jun 2014, Robert O'Callahan wrote:
>
>
>
>
>
> the elements "s" and "i" are put in the HTML namespace already.
As siblings of the element, though, not descendants.
This was required to get some level of compatibility with deployed content
while still allowing in HTML. There was
On 6/26/14, 10:39 AM, Tim Marinin wrote:
If not, then why we need for css, only for legacy reasons?
Pretty much, yes. If
2014-06-26 14:12 GMT+04:00 Anne van Kesteren :
> On Thu, Jun 26, 2014 at 12:08 PM, Tim Marinin
> wrote:
> > I propose exact the same behaviour, as
Hadn't thought of that. object-fit seems smells dangerous. I think we may
need to define explicit behaviors for renderedPixelWidth/Height for the
different object fit modes.
For example, with 'object-fit: contains', will the renderedPixelWidth/Height
be computed in a way to fill the element's conte
On Thu, Jun 26, 2014 at 11:06 AM, Tim Marinin wrote:
> Most often use for tag
Most often use for tag
43 matches
Mail list logo
