remove nuking of hash changes when hash is disabled
This commit is contained in:
parent
772fa0308d
commit
ba0b367ed9
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
|
@ -131,12 +131,16 @@ export default class Location {
|
|||
else if( config.hash ) {
|
||||
window.history.replaceState( null, null, '#' + this.getHash() );
|
||||
}
|
||||
// UPDATE: The below nuking of all hash changes breaks
|
||||
// anchors on pages where reveal.js is running. Removed
|
||||
// in 4.0. Why was it here in the first place? ¯\_(ツ)_/¯
|
||||
//
|
||||
// If history and hash are both disabled, a hash may still
|
||||
// be added to the URL by clicking on a href with a hash
|
||||
// target. Counter this by always removing the hash.
|
||||
else {
|
||||
window.history.replaceState( null, null, window.location.pathname + window.location.search );
|
||||
}
|
||||
// else {
|
||||
// window.history.replaceState( null, null, window.location.pathname + window.location.search );
|
||||
// }
|
||||
}
|
||||
|
||||
}
|
||||
|
|
Loading…
Reference in New Issue