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
Hello.
I'm reading this part:
http://www.whatwg.org/specs/web-apps/current-work/#focus
The intro states:
When an element is focused, key events received by the document must be
targeted at that element. There is always an element focused; in the
absence of other elements being focused, the
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
I am agaist using compound attributes like this; make it 16times;16 if you
insist.
Best regards,
Chris
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Maciej Stachowiak
Sent: Wednesday, April 30, 2008 7:13 AM
To: Ian Hickson
Cc: [EMAIL PROTECTED]
Subject:
I have a concern about 3.5.3 Scrolling elements into view:
http://www.whatwg.org/specs/web-apps/current-work/multipage/section-interaction.html#scrollintoview
In addition to concerns expressed by Brad Fults
(http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2007-October/012655.html),
I
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,
It was brought up during the latest postMessage patching in Mozilla that the
HTML5-mandated origin for file: URIs groups all local file system pages into a single
origin. Pages are increasingly being used in application-like contexts, and if Java is
any example, grouping all files into the
On Wed, Apr 30, 2008 at 10:58 AM, David Bolter [EMAIL PROTECTED]
wrote:
Specifically I would ask that:
1. scrollIntoView not do anything in the case that the element is already
fully visible (possibly in the middle of the viewport), or
2. ensureElementIsVisible to be added as described by
Brady Eidson wrote:
what are people's thoughts on adding a new element for icon
badging, one that would only be valid within the head?
Funny I wrote just that same question to the editor an hour ago.
Since someone else brought it up, now I'm just adding to the
thought. :-)
The idea of an
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
Peter Kasting wrote:
On Wed, Apr 30, 2008 at 10:58 AM, David Bolter
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote:
Specifically I would ask that:
1. scrollIntoView not do anything in the case that the element is
already fully visible (possibly in the middle of the viewport), or
On Wed, 30 Apr 2008, Jeff Walden wrote:
It was brought up during the latest postMessage patching in Mozilla that
the HTML5-mandated origin for file: URIs groups all local file system
pages into a single origin. Pages are increasingly being used in
application-like contexts, and if Java is
On Thu, 24 Jan 2008, Adam Barth wrote:
The security origin of frames that begin life with the URL about:blank
or differs in different browsers. In Firefox and the trunk revision
of WebKit, the principal for the frame is aliased to the principal of
the frame's parent (or opener, if it is a
-Original Message-
From: Ian Hickson [EMAIL PROTECTED]
Sent: Apr 29, 2008 9:52 PM
To: [EMAIL PROTECTED]
Subject: [whatwg] link rel=icon width= height=
(With my rarely-used Google hat on:)
The Gears team has an API that allows authors to specify a set of icons:
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
On Wednesday 2008-04-30 13:58 -0400, David Bolter wrote:
1. scrollIntoView not do anything in the case that the element is already
fully visible (possibly in the middle of the viewport), or
2. ensureElementIsVisible to be added as described by Daniel Glazman
On Wed, 30 Apr 2008, Jonas Sicking wrote:
The aliasing behaviour seems really dodgy. I've specced the copying
behaviour, which also matches Opera.
The reason you want to use aliasing is in a situation like this (file
loaded from www.example.com) :
html
body
iframe id=f/iframe
* 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)
Ian Hickson wrote:
On Wed, 30 Apr 2008, Jonas Sicking wrote:
The aliasing behaviour seems really dodgy. I've specced the copying
behaviour, which also matches Opera.
The reason you want to use aliasing is in a situation like this (file
loaded from www.example.com) :
html
body
iframe
L. David Baron wrote:
On Wednesday 2008-04-30 13:58 -0400, David Bolter wrote:
1. scrollIntoView not do anything in the case that the element is already
fully visible (possibly in the middle of the viewport), or
2. ensureElementIsVisible to be added as described by Daniel Glazman
Firefox seems to have an internal check for isElementInView, because
calling scrollIntoView(false) after scrollIntoView(true) does nothing.
e.g. scroll only if it's not visible at all
Firefox 2 uses:
scrollIntoView(true)
scroll the element and its containers vertically such that the
32 matches
Mail list logo
