[whatwg] URL resolution of fragment urls in html5 webapps

The current url resolution as describedin 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 (link) and fragment/a

Re: [whatwg] URL resolution of fragment urls in html5 webapps

uld be resolved against document.baseURI (which is tied to location.href unless base[href] is set) - 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 > >

Re: [whatwg] URL resolution of fragment urls in html5 webapps

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 wrote: > > > > On Wed, Jul 10, 2013

Re: [whatwg] URL resolution of fragment urls in html5 webapps

nt document. Check out this simple document: - code+preview: http://plnkr.co/edit/TtH7rjQVKU6qN0QOxULW?p=preview - preview only: http://run.plnkr.co/bY3fF8OOXKq5MrSu/ pushState is just an easy way how you can get into situation where the url of the current document changes, and base[href] preven

Re: [whatwg] URL resolution of fragment urls in html5 webapps

On Thu, Jul 25, 2013 at 3:09 PM, Jonas Sicking wrote: > On Thu, Jul 18, 2013 at 8:42 AM, Igor Minar wrote: > > > > > > > > On Thu, Jul 18, 2013 at 2:13 AM, Jonas Sicking wrote: > >> > >> On Wed, Jul 10, 2013 at 10:24 AM, Alex Russell > &

Re: [whatwg] URL resolution of fragment urls in html5 webapps

On Thu, Jul 25, 2013 at 4:14 PM, Jonas Sicking wrote: > On Thu, Jul 25, 2013 at 4:04 PM, Igor Minar wrote: > > > > On Thu, Jul 25, 2013 at 3:09 PM, Jonas Sicking wrote: > >> > >> On Thu, Jul 18, 2013 at 8:42 AM, Igor Minar wrote: > >> > > &g

Re: [whatwg] Proposal: Specify SHA512 hash of JavaScript files in

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, angul

Re: [whatwg] PSA: Chrome ignoring autocomplete="off" for Autofill data

Are you going to properly fire change&input 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 dev

Re: [whatwg] PSA: Chrome ignoring autocomplete="off" for Autofill data

, 2014 at 8:22 PM, Igor Minar wrote: > >> Are you going to properly fire change&input events when autofill happens? >> >> The current autofill behavior is causing major headaches for application >> and framework developers and by ignoring autocomplete attribute you di

Re: [whatwg] PSA: Chrome ignoring autocomplete="off" for Autofill data

fire 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 wrote: > I believe so, but I'll double check and will email you off this thread. > > \i > > > On Thu Nov