easytabs:before and easytabs:after do not fire if a tab is selected via URL hash

[ghost]

I'm not sure if this is intentional or not, but it does cause me to need a number of workarounds.

As an example, let's say we have One.html and Two.html. Two.html has an easytabs structure, like #tabs-1, #tabs-2, etc. One.html has a link to Two.html#tabs-2. If you were to click on that link, easytabs:before and easytabs:after aren't triggered.

If you are already on Two.html and you go to #tabs-2 via editing the URL, it does trigger.

This causes problems because I've written a number of structures around easytabs, like disabled tabs and sub-tabs. Those don't get their routines run, so refusing entry to a disabled tab and styling a sub-tab don't happen when coming from another page. I've tried triggering easytabs:after manually when there's a hash, but it doesn't happen at the right time.

[justin-arvay]

+1 for this.

Callbacks should call on page load (initialization) as well. Easy enough to work around but would be nice if it was built in. Could provide the ability to disable that functionality.