Tabs options: .selected vs .cookie priority
If .selected and .cookie options are set simultaneously when
initializing tabs, it would seem logical to me to give the priority
to .selected option (in other words, .cookie should be ignored
if .selected is specified). Currently it's not the case, and
specifying both options _in some cases_ gives me unpredictable
results. I can't precisely understand the behavior, but depending on
the last tab number stored in a cookie, and depending on the .selected
value, sometimes it works, but sometimes surprisingly completely
different tab is selected on load (neither .selected nor .cookie).
Currently the only workaround is branching in the code
(dropping .cookie whenever I want to explicitly specify a tab
via .selected). Not that it's a big issue, but still...