Try to use replaceState to verify history API.

[stevemckenzie]

#535

[mjackson]

I think we need a way to do this without using replaceState because AFAICT it may trigger another request.

@stevemckenzie navigator.userAgent ? :P

[mjackson]

@stevemckenzie do you have a sample User-Agent string from browsers that currently fail the check?

[gaearon]

When would replaceState trigger a request? Do you mean buggy browsers?

[mjackson]

Oh, wait. Sorry. I wasn't thinking straight. @stevemckenzie @gaearon Please ignore me :)

[gaearon]

I'm still not sure about the implications in case this check happens when HashLocation is used.
It's a bit weird for a “getter” method to have side-effect like this.

Are we sure that window.location.pathname + window.location.search is precisely current path?

[stevemckenzie]

I definitely agree that this would be better without using replaceState but from everything I tried using the latest version of Firefox, this was basically the only working route I found.

with @gaearon 's last comment, I guess location.hash should be included?

[tiye]

Does it mean we can use history.replaceState {}, '', 'a-route' to trigger react-router re-rendering?

[ryanflorence]

I borrowed that code from modernizr, has it changed there?

[stevemckenzie]

Modernizr/Modernizr#1463

[stevemckenzie]

@mjackson - I updated this a bit based on what we talked about at the conf. I didn't think this would become a priority again for a while but it now has for me.

For now I'm just using my fork though.

[ryanflorence]

Have you experiemented with an iframe as mentioned in Modernizr/Modernizr#1463?

[ryanflorence]

@stevemckenzie ping ^

[ryanflorence]

closing due to inactivity, please holler if we should reopen this.