On 7/8/2013 8:33 PM, Alex Bishop wrote:
I imagine that it’s an early Netscape implementation detail that
escaped into the wild. Given that I can still remember pipes in file
URLs 15+ years later, I would not be surprised if other people rely on
this working.
I am certain that we must
Conversely, if it helps to bring the spec closer to the implementations,
one thing we do not intend to implement in Chrome is the automatic high-DPI
canvas scaling (ie., auto-doubling of backing stores, getImageDataHD(),
putImageDataHD(), etc).
I believe Apple has also announced that they are
On Sun, Mar 31, 2013 at 10:33 AM, Anne van Kesteren ann...@annevk.nl wrote:
There are a couple of scenarios http://notifications.spec.whatwg.org/
does not address at the moment.
A) User navigates to chat site. Chat site creates a notification from
a chat with P while the user does something
Yes, those should be taken out.
On Tue, Jul 9, 2013 at 8:40 AM, Stephen White senorbla...@chromium.orgwrote:
Conversely, if it helps to bring the spec closer to the implementations,
one thing we do not intend to implement in Chrome is the automatic high-DPI
canvas scaling (ie., auto-doubling
On Mon, Jul 8, 2013 at 6:23 PM, Peter Kasting pkast...@google.com wrote:
Given how unlikely it is that someone will have registered a scheme handler
for the one-character drive letters, the Chrome/IE behavior seems more
forgiving and more likely what the author wants, to me.
But it also forks
On Tue, Jul 9, 2013 at 10:57 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Mon, Jul 8, 2013 at 6:23 PM, Peter Kasting pkast...@google.com wrote:
Given how unlikely it is that someone will have registered a scheme
handler
for the one-character drive letters, the Chrome/IE behavior seems
A topic that regularly comes up is script loading.
I sent an e-mail responding to related feedback last year, though it
didn't get any replies to the script loading parts of it:
http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Dec/0221.html
It seems that people want something
This is a long and complicated topic with lots of history. Please bear with
the length of my reply.
It seems that people want something that:
- Lets them download scripts but not execute them until needed.
- Lets them have multiple interdependent scripts and have the browser
manage
On 7/9/13, Ian Hickson i...@hixie.ch wrote:
A topic that regularly comes up is script loading.
Yes, for years it has come up.
I jumped on the topic around 2009 here and on comp.lang.javascript to
add the idea about chain of responsibility to this solution.
The chain of responsibility pattern
But I'd settle for anything, no matter how complex, as long as it actually
solves the many use cases. Your proposed option has potential, as long as
the missing event part is addressed.
It seems to me that from an IE-perspective, the only missing piece is the
event itself.
Well,
I just joined the list and glad this subject is brought up.
I have been wrestling pretty hard with script loading issues lately. I'd
say that having the browser manage script interdependency is probably a
bad and cumbersome way to solve these issues. I'll try to explain,
talk about the defer
I have been wrestling pretty hard with script loading issues lately. I'd
say that having the browser manage script interdependency is probably a
bad and cumbersome way to solve these issues.
What do you mean by having the browser manage script interdependency? As far
as I am aware, this
12 matches
Mail list logo
