kiwix-js
kiwix-js copied to clipboard
kiwix
Recent stackexchange ZIM files have broken responsive design in jQuery mode
https://mirror.download.kiwix.org/zim/.hidden/dev/alcohol_meta_stackexchange_com_2021-08.zim has a responsive design : the Questions/Tags/Users/About items that appear on the left side on large screens should be moved at the top on smaller screens :
-
With a large window/screen, the header looks like this :
-
With a smaller window/screen ((width<=640px), it should look like this :
In ServiceWorker mode, it works fine (even if I find the difference surprising, see https://github.com/openzim/sotoki/issues/237)
But in jQuery mode, the left panel remains in small screens :
I initially thought it was because of some javascript handling (unsupported in jQuery mode), but @rgaudin says javascript is not used for that (see https://github.com/openzim/sotoki/issues/237#issuecomment-903233613)
We should investigate to see where it comes from. If it's something we can't easily fix in kiwix-js, it might be still time to ask for a change on sotoki (if it's not complicated).
I wonder if this has anything to do with the order in which CSS is loaded and applied. Very wild guess.
We finally are refreshing all StackExchange ZIM files (180 of them) with version 2.0.0 of Sotoki. Therefore, from now, this bug will have more impact.
I confirm this issue is still present (jQuery mode only) in Stack Exchange ZIMs produced this month (yesterday). I tested with french_stackexchange_com_2022-05.zim. The issue seems to come from the fact that the the inner divs do not in fact resize when the page as a whole is resized. The same issue affects KJSW (in jQuery mode only).
Bug is still there in 3.6.0 with beer.stackexchange.com_en_all_2022-11.zim, but really wonder this is worth investigating considering that SW mode is default one and we priority is not anymore to fix bugs in JQuery mode.
I confirm. It's clearly not a problem with the ZIM, because it affects only jQuery mode. I agree it's not worth fixing for JQuery mode only. This is therefore very low priority. I'll close it as wontfix.