SCENARIOThe web app workflow is the following:

Someone clicks on a a href element into a page. The link is followed and then another page within the site is reached. The link URL also contains a hash var.

(This hash var is what I intended to use in order to achieve the next point)

There is a content grid that must show the wanted part, this object was built with an out of the box CMS, so I preferably don't want to modify it. This also, only works when the user clicks on the very button filter.

(This filter is based entirely on events and not on "GUI visible" locations, thus I'm not able to call for an specific filter from the very url, the previous object -there was a previous object, yes- worked really good with hashes from URL, but the new doesn't.)

The content grid filter elements don't have any ids, they just have a data custom attribute to be identified.

And that's it.

The workaround is intended to be like this:

$( window ).load(function() { var filter = window.location.hash.substr(1); if(filter == "keywordA") { $('a[data-filter=".cat-1"]').trigger('click'); } if(filter == "keywordB"){ $('a[data-filter=".cat-2"]').trigger('click'); } if(filter == "keywordC"){ $('a[data-filter=".cat-3"]').trigger('click'); } if(filter == "keywordD"){ $('a[data-filter=".cat-4"]').trigger('click'); } if(filter == "keywordE"){ $('a[data-filter=".cat-5"]').trigger('click'); } });

Then, dark and unknown forces comes into place, because when I enter this in the address bar: the DOM works well, as expected. The content grid displays exactly what I want.

But when I try to reach the same link but from an a href element within it just doesn't do anything at all.


I used window.load because that way the function is forced to be executed once everything is settled in the DOM, and after every single code instance of $(document).ready() functions, because the website already works with many of these.

Here's the problem:When navigating from the a link to a different link that is the same page, but has a different hash var, like , the site doesn't actually reload. This is default behaviour, because it's meant to jump to the element on the page with the id of the hash.

Luckily, there is an event for hash changes on the site.


Now depending on how your filtering works, you might want to call a function that does all the filtering (the one that does it on loading the page), or, if this is a server-side CMS thing, you might want to reload the page.

$(window).bind('hashchange', function(e) { // Enter your filter function here doFiltering(); });

or if reloading the page is more appropritate.

$(window).bind('hashchange', function(e) { document.location.reload(); });

I don't quite understand what you mean by "This filter is based entirely on events and not on 'GUI visible' locations", so you might want to elaborate a little more in a comment, if I misunderstood you, but I hope either one of these soloutions work for you.

本文前端(javascript)相关术语:javascript是什么意思 javascript下载 javascript权威指南 javascript基础教程 javascript 正则表达式 javascript设计模式 javascript高级程序设计 精通javascript javascript教程

本文标题:Why window.load does not work when the request comes from outside t ...

技术大类 技术大类 | 前端(javascript) | 评论(0) | 阅读(36)