any events.
Things are still pretty broken for many end users but we've already made
major progress. Yay!
\i
On Fri Nov 14 2014 at 8:12:33 AM Igor Minar imi...@google.com wrote:
I believe so, but I'll double check and will email you off this thread.
\i
On Thu Nov 13 2014 at 11:06:37 PM Evan
, 2014 at 8:22 PM, Igor Minar imi...@google.com wrote:
Are you going to properly fire changeinput events when autofill happens?
The current autofill behavior is causing major headaches for application
and framework developers and by ignoring autocomplete attribute you disable
the only way
Are you going to properly fire changeinput events when autofill happens?
The current autofill behavior is causing major headaches for application
and framework developers and by ignoring autocomplete attribute you disable
the only way developers can work around this bug.
On angular we had to
I like this a lot!
I've been in discussions in the past where developers expressed concerns
about inability to verify that the bits delivered from CDN were the same
bits as the ones they reviewed and tested against during development.
It's very common to pull popular libraries (like jquery,
On Thu, Jul 25, 2013 at 3:09 PM, Jonas Sicking jo...@sicking.cc wrote:
On Thu, Jul 18, 2013 at 8:42 AM, Igor Minar imi...@google.com wrote:
On Thu, Jul 18, 2013 at 2:13 AM, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Jul 10, 2013 at 10:24 AM, Alex Russell slightly...@google.com
On Thu, Jul 25, 2013 at 4:14 PM, Jonas Sicking jo...@sicking.cc wrote:
On Thu, Jul 25, 2013 at 4:04 PM, Igor Minar imi...@google.com wrote:
On Thu, Jul 25, 2013 at 3:09 PM, Jonas Sicking jo...@sicking.cc wrote:
On Thu, Jul 18, 2013 at 8:42 AM, Igor Minar imi...@google.com wrote
Controller and it would definitely
help if the in-document navigation was something that I could control with
it. But ideally, I shouldn't need to do anything for the in-document
navigation to work.
On Wed, Jul 10, 2013 at 11:14 AM, Igor Minar imi...@google.com wrote:
On Wed, Jul 10, 2013 at 10:24
into situation where the url
of the current document changes, and base[href] prevents all in-document
links to resolve correctly.
/i
/ Jonas
On Wed, Jul 10, 2013 at 7:11 AM, Igor Minar imi...@google.com wrote:
The current url resolution as
described
http://www.whatwg.org/specs/web-apps
The current url resolution as
describedhttp://www.whatwg.org/specs/web-apps/current-work/#resolving-urlsin
the spec results in some unhelpful behavior when the following
combination of web technologies are used in a client-side web app:
- a combination of path-relative urls (a
)
- relative anchor urls should always resolve against location.href
I think that this kind of behavior would make the url resolution work in
all common and currently used scenarios.
/i
Regards
On Wed, Jul 10, 2013 at 7:11 AM, Igor Minar imi...@google.com wrote:
The current url resolution
10 matches
Mail list logo
