Captions should stay put like regular content, as they're labels
for the table as a whole.
Acts kind of weird (jumpy) when the table is flowing off the page,
but totally stationary when whole table fits on page. Not sure
what this means.
Bug: T269912
Change-Id: I9df25315280aaae59dd06ec36f99832576c0c24c
No more overflow, but still scrollable. WHOO.
This is probably awful, but apparently I'm at least more capable
than I thought. That's probably not saying much.
Bug: T270050
Change-Id: Ieb7d2d756d4dad6ae8713edd2a1f19880420916b
Also, like, maybe only trigger on top-level tables? Hopefully that
stops it from breaking everything... as much. Probably.
Bug: T269912
Bug: T269913
Change-Id: I09170d7dc67c49df4c010584ef0633a94659f29b
It's called shitty js. Affordance to label overflow is slightly wrong
for current behaviour, as it basically presents as a toggle. Maybe it
should toggle something! Like popouts, that would be fun. I'unno.
Slightly more framing on wikitables etc, but apply to all tables,
because why not.
Rejig to come with actual popouts or stuff...
Bug: T179265
Bug: T265785
Change-Id: I607cb87687fcbcb481dc2fb7165c52b9e9c35873
This feature was copied from Vector where it was recently removed
in e5c837e3ebf8.
In a nut shell, HTML output from PHP generally either has no
tabindex, tabindex=0 or tabindex=-1, or sometimes numbers between
1-100 for custom tab ordering. In JavaScript we then used
lastTabIndex (returns highest+1) to get an input field to be at the
end of the tab order. Thus making it be the *first* thing that
gets focussed when pressing Tab on a page (I guess the browser
offset is at the end of the document by default?)
This JS-based approach wasn't very stable as it required only
other thing in JS to use it for other reasons (e.g. genuinely
minting normal-use tab indexes for something) to break it as
we can't use the same logic for both "the lowest next number"
and "the highest possible number".
If we want to preserve this feature, it should probably do
something like attr('tabindex', '99999') which, while ugly,
would be a more sustainable way to implement this this.
Per Jack Phoenix in code review on this patch, match Vector
behaviour for now, where it was removed per T226148 for
being contrary to accessibility best practies.
Bug: T234581
Change-Id: I24777bdb6655f21d2f4896d5f887a125b36ab584
Kill js solution even for other browsers because it doesn't even really
work to begin with. And I have no clue how to make it work, because I
can't find any examples that do, either.
Fixes current firefox and chrome. Users of old browsers/other
proprietary or whatever things can, uh, suffer, I guess.
Bug: T181484
Change-Id: Ic3415702eaa33cf56ed0b1fabf9ca607c88d1863
Prevent anchors from putting headers, cite notes, etc behind fixed
header when jumping around. Use js to avoid previous issue of mucked
up highlighting... (T162649)
bug: T181484, T162649
Change-Id: I6bdb450b24df50f39e14bc2b254c6adb6cc7f7d7
When using the Vector skin, and you load a page and press the tab
button on the keyboard once, the cursor focus on the search box,
this is handy and now available on the timeless skin too.
Also, removed target "mobile" as "jquery.tabIndex" dependency doesn't
use it.
Bug: T201424
Change-Id: I6e5d96371b5342ad2d3a207e980ec1fcf7e2de99
Isarra
RetroCraft
Timo Tijhof
Fomafix
Ed Sanders
Alangi Derick