#3941 return decoded hash in getHash()

[bobmop]

...to compare correctly to cached fragment in navigate()

[akre54]

@braddunbar ?

[braddunbar]

This seems fine to me. I'd say it could even be moved up into getFragment since getPath calls decodeFragment too.

[bobmop]

The methods getPathand getHash are also called separately. I can't figure out the influence...

[megawac]

I'm fine with this but it may be a minor breaking change. I'd consider it a bug fix personally though

[barceyken]

We added this to our project too 👍

[haleo9000]

This seems to break browsers 'back' navigation button. However, it does fix the above stated problem.

[jashkenas]

This seems to break browsers 'back' navigation button. However, it does fix the above stated problem.

Uh.

[platinumazure]

It'd be great to have normalized hash decoding behavior, but the bit about breaking a browser's "back" button is highly concerning.

• Have we established the exact impact (which browsers are affected)?
• Does anyone know why that happens?
• Is that issue fixable, or is this the wrong direction?

[Daniel-Alonso-Exabeam]

This issue is related to #4132
I have proposed my own solution in that thread, please take a look!

[jgonggrijp]

Rejecting this as it is a breaking change and it seems to cause worse problems than it aims to solve.