Ian Hickson wrote:
Using media queries for this is serious overkill. I can easily imagine
uses for this that are from code that doesn't have a media queries
implementation available, and this isn't something that implementors are
going to implement media queries for. We need a solution that
The integers should be separated by times; and not by x. In case you
care about semantics, that is.
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Ian Hickson
Sent: Thursday, May 08, 2008 4:18 AM
To: WHATWG
Subject: [whatwg] link rel=icon width=
There's no need to request things more than once -- I base my editing
decisions on the quality of the arguments put forward, not the quantity.
By all means, if you have new information, bring it forward, but merely
repeating what has already been said doesn't do anything.
I'm sorry. I missed
On Thu, 08 May 2008 03:17:38 +0100, Ian Hickson [EMAIL PROTECTED] wrote:
I've added a sizes attribute to link for the icon keyword.
The spec now contains:
If multiple icons are provided, the user agent must select the most
appropriate icon according to the media and sizes attributes. If
I think specifying aspect ratio and specifying duration of sound
clip are less compelling information to provide than icon sizes.
We haven't had any requests for anything but height/width.
An in the SVG case, if you have a height/width you already have the aspect
ratio anyway.
-- Charles
On Wed, May 7, 2008 at 7:17 PM, Ian Hickson [EMAIL PROTECTED] wrote:
I've added a sizes attribute to link for the icon keyword. It takes
a space separated list of keywords consisting of two integers separated by
an x or the keyword any.
Cool. Thanks for being so responsive on this.
- a
On Wed, 30 Apr 2008 03:52:08 +0200, Ian Hickson [EMAIL PROTECTED] wrote:
(With my rarely-used Google hat on:)
The Gears team has an API that allows authors to specify a set of icons:
http://code.google.com/apis/gears/upcoming/api_desktop.html
They used a scripted API, but when I tried to
I don't think it's that important to specify exact icon sizes. Authors
won't bother to accurately provide such detailed information, and
applications don't need it anyway.
iPhone shouldn't be a concern here. It isn't limited to 59x60
icons—Apple's own website uses 129x129
On Mon, May 5, 2008 at 1:57 PM, Kornel Lesinski [EMAIL PROTECTED] wrote:
There isn't much bandwidth to be saved. These icons are going to be
downloaded only once. 128x128 PNG icons take only 20-30kb.
Without hints as to which file contains which size, the user agent
must download up to four
On Mon, 05 May 2008 23:36:51 +0100, Aaron Boodman [EMAIL PROTECTED] wrote:
There isn't much bandwidth to be saved. These icons are going to be
downloaded only once. 128x128 PNG icons take only 20-30kb.
Without hints as to which file contains which size, the user agent
must download up to four
Maciej Stachowiak wrote:
By contrast, I do not know of any actual need to determine the aspect
ratio of an SVG icon or the duration of a sound icon. I do not know of
cases where HI guidelines for particular platforms would recommend
different choices of icon aspect ratio or sound icon
On Sat, May 3, 2008 at 8:13 AM, fantasai [EMAIL PROTECTED] wrote:
Maciej Stachowiak wrote:
By contrast, I do not know of any actual need to determine the aspect
ratio of an SVG icon or the duration of a sound icon. I do not know of cases
where HI guidelines for particular platforms would
Maciej Stachowiak wrote:
OK, I'm sure the last thing that is needed is more syntax suggestions,
but here's an alternate proposal with no new attributes, specify size
info as additional rel keywords:
link rel=icon scalable type=application/svg href=whatwg.svg
link rel=icon 16x16 32x32
Maciej Stachowiak wrote:
This might require that existing browsers cope correctly (or exploit
duplication/error behaviors), but could a MIME parameter address this
without needing another attribute at all? That's the most narrowly
scoped change I can imagine that would address the need.
On May 2, 2008, at 12:24 AM, fantasai wrote:
Maciej Stachowiak wrote:
This might require that existing browsers cope correctly (or
exploit duplication/error behaviors), but could a MIME parameter
address this without needing another attribute at all? That's the
most narrowly scoped
Cc: [EMAIL PROTECTED]; Jeff Walden
Subject: Re: [whatwg] link rel=icon width= height=
My first example (the SVG) could be used anywhere if UA understands
SVG and can render down to the specific sizes needed by the computing
environment. But it may not be feasible for all artwork to be provided
Lachlan Hunt wrote:
Martin Atkins wrote:
Lachlan Hunt wrote:
For color, you are reinventing Media Queries. For compression, you
are basically reinventing q values for MIME types.
link type=image/png;q=1.0 media=all and (min-color:8)
link type=image/jpeg;q=0.8 media=all and (min-color:8)
Martin Atkins wrote:
Lachlan Hunt wrote:
Martin Atkins wrote:
Could this be said about size as well?
link type=image/png
media=all and (max-width:16px and max-height:16px)
No, because the media queries are related to the actual tech specs of
the device, not the image. I'm fairly
On Apr 29, 2008, at 10:13 PM, Maciej Stachowiak wrote:
I would suggest a sizes attribute which can take a list of sizes
(with x as a width/height separator), or a keyword such as any or
scalable to indicate a scalable format suitable for any size.
link rel=icon type=application/svg
Ian Hickson wrote:
This is a proposal to add height and width attributes to link
specifically for the case of rel=icon, so that authors can provide
multiple icons and let the UA decide which to use based on their size
(without having to download them all to find out which is best).
Opinions?
On Apr 29, 2008, at 10:24 PM, Charles Iliya Krempeaux wrote:
Hello,
On Tue, Apr 29, 2008 at 10:13 PM, Maciej Stachowiak [EMAIL PROTECTED]
wrote:
On Apr 29, 2008, at 6:52 PM, Ian Hickson wrote:
[...]
link type=icon type=application/svg sizes=any
href=whatwg.svg
link type=icon
On Apr 29, 2008, at 10:33 PM, Michael(tm) Smith wrote:
Ian Hickson [EMAIL PROTECTED], 2008-04-30 01:52 +:
The Gears team has an API that allows authors to specify a set of
icons:
http://code.google.com/apis/gears/upcoming/api_desktop.html
They used a scripted API, but when I tried
On Apr 29, 2008, at 11:17 PM, Jeff Walden wrote:
Ian Hickson wrote:
This is a proposal to add height and width attributes to link
specifically for the case of rel=icon, so that authors can provide
multiple icons and let the UA decide which to use based on their
size
(without having to
Hello,
On Tue, Apr 29, 2008 at 11:24 PM, Maciej Stachowiak [EMAIL PROTECTED] wrote:
On Apr 29, 2008, at 10:24 PM, Charles Iliya Krempeaux wrote:
Hello,
On Tue, Apr 29, 2008 at 10:13 PM, Maciej Stachowiak [EMAIL PROTECTED] wrote:
On Apr 29, 2008, at 6:52 PM, Ian Hickson wrote:
On Apr 29, 2008, at 11:54 PM, Charles Iliya Krempeaux wrote:
I don't really prefer one to the other, just considering the
possibilities we have at hand.
My current thinking is that you can go one of 2 ways.
#1: Pack everything into in link element. (I.e., what you were
suggesting.)
Hello,
On Wed, Apr 30, 2008 at 12:19 AM, Maciej Stachowiak [EMAIL PROTECTED] wrote:
On Apr 29, 2008, at 11:54 PM, Charles Iliya Krempeaux wrote:
[...]
In practice, these things usually do not matter when using an icon in the
user interface. But the sizes available do matter. I would not
On Apr 30, 2008, at 12:41 AM, Charles Iliya Krempeaux wrote:
Hello,
On Wed, Apr 30, 2008 at 12:19 AM, Maciej Stachowiak [EMAIL PROTECTED]
wrote:
On Apr 29, 2008, at 11:54 PM, Charles Iliya Krempeaux wrote:
[...]
In practice, these things usually do not matter when using an icon
in
On Wed, Apr 30, 2008 at 8:33 AM, Michael(tm) Smith [EMAIL PROTECTED] wrote:
I notice the docs for the icons param of the Gears createShortcut()
method describe four discrete sizes that all have the same height
and width (An object containing one or more of these named
properties: 128x128,
Charles Iliya Krempeaux wrote:
link rel=enclosure type=image/xxx width=640 height=480
compressioning=lossy coloring=truecolor href=A.xxx
link rel=enclosure type=image/xxx width=1280 height=960
compressioning=lossy coloring=truecolor href=A.xxx
link rel=enclosure type=image/xxx width=2560
Ian Hickson wrote:
(With my rarely-used Google hat on:)
The Gears team has an API that allows authors to specify a set of icons:
http://code.google.com/apis/gears/upcoming/api_desktop.html
They used a scripted API, but when I tried to get them to use a
declarative API, they said that the
Lachlan Hunt wrote:
Charles Iliya Krempeaux wrote:
link rel=enclosure type=image/xxx width=640 height=480
compressioning=lossy coloring=truecolor href=A.xxx
link rel=enclosure type=image/xxx width=1280 height=960
compressioning=lossy coloring=truecolor href=A.xxx
link rel=enclosure
: Re: [whatwg] link rel=icon width= height=
link type=icon type=image/microsoft.vnd.icon sizes=16x16 32x32
href=whatwg.ico
Regards,
Maciej
Following this thread, I just decided to throw this out there to see
if I'm way off base or not...
Since this is obviously a topic that has sparked a tad of passionate
interest and there's not necessarily a clear solution that doesn't
make link ugly, what are people's thoughts on adding a
On Wed, Apr 30, 2008 at 11:32 AM, Brady Eidson [EMAIL PROTECTED] wrote:
Since this is obviously a topic that has sparked a tad of passionate
interest and there's not necessarily a clear solution that doesn't make
link ugly, what are people's thoughts on adding a new element for icon
badging,
Of Brady Eidson
Sent: Wednesday, April 30, 2008 11:32 AM
To: WHATWG Mailing List
Cc: Ian Hickson
Subject: Re: [whatwg] link rel=icon width= height=
Following this thread, I just decided to throw this out there to see
if I'm way off base or not...
Since this is obviously a topic that has sparked
Martin Atkins wrote:
Lachlan Hunt wrote:
For color, you are reinventing Media Queries. For compression, you are
basically reinventing q values for MIME types.
link type=image/png;q=1.0 media=all and (min-color:8)
link type=image/jpeg;q=0.8 media=all and (min-color:8)
Could this be said
On Apr 30, 2008, at 11:32 AM, Brady Eidson wrote:
Following this thread, I just decided to throw this out there to see
if I'm way off base or not...
Since this is obviously a topic that has sparked a tad of passionate
interest and there's not necessarily a clear solution that doesn't
* Lachlan Hunt wrote:
Martin Atkins wrote:
Lachlan Hunt wrote:
For color, you are reinventing Media Queries. For compression, you are
basically reinventing q values for MIME types.
link type=image/png;q=1.0 media=all and (min-color:8)
link type=image/jpeg;q=0.8 media=all and (min-color:8)
On Tue, Apr 29, 2008 at 6:52 PM, Ian Hickson [EMAIL PROTECTED] wrote:
This is a proposal to add height and width attributes to link
specifically for the case of rel=icon, so that authors can provide
multiple icons and let the UA decide which to use based on their size
(without having to
On Apr 29, 2008, at 6:52 PM, Ian Hickson wrote:
(With my rarely-used Google hat on:)
The Gears team has an API that allows authors to specify a set of
icons:
http://code.google.com/apis/gears/upcoming/api_desktop.html
They used a scripted API, but when I tried to get them to use a
Hello,
On Tue, Apr 29, 2008 at 10:13 PM, Maciej Stachowiak [EMAIL PROTECTED] wrote:
On Apr 29, 2008, at 6:52 PM, Ian Hickson wrote:
[...]
link type=icon type=application/svg sizes=any href=whatwg.svg
link type=icon type=image/microsoft.vnd.icon sizes=16x16 32x32
href=whatwg.ico
link
Ian Hickson [EMAIL PROTECTED], 2008-04-30 01:52 +:
The Gears team has an API that allows authors to specify a set of icons:
http://code.google.com/apis/gears/upcoming/api_desktop.html
They used a scripted API, but when I tried to get them to use a
declarative API, they said that
42 matches
Mail list logo
