zakius

coming back with another case: https://pl.wikipedia.org/wiki/Izolator_Boguchwała apparently can appear in text and will be handled properly by browsers but is parsed as https://pl.wikipedia.org/wiki/Izolator_Boguchwa by WT `(\b(https?|ftp|file)://[-\p{L}\p{M}*+0-9+&@#/%?=~_|$!:,.;()\[\]]*)` would work in Golang,...

that may be a reasonable idea actually, fast and basically covers everything that can be covered with more complex options, even if it can sometimes get a bit too eager...

I wonder if optimizing keyboard navigation wouldn't cover most usecases already, depending on the way TV/STB interprets inputs from remote that may just work

update: it seems gestures are working, but rockers can't, I managed to set up everything like I needed to, but you may want to take a look at it

I definitely would like all of them to be configurable, especially that even when I do move to 11 in few years I'll get rid of rounded corners for sure...

by the screens itself it looks like everything is done according to license, but if you have access to the software can you verify if the source code of the...

on the screens you provided there is a link to source code but it's not clear if it links here or to the derived code being open source, including GNU...

if you want to have any meaningful comparison you should use the same engine, Chromium based browsers tends to fare much better and improved compilation flags won't be enough to...

something like this seems to work ``` [class^="scroller"]>[class^="listItem"]:nth-last-child(3),[class^="scroller"]>[class^="listItem"]:nth-last-child(2),[class^="scroller"]>[class^="listItem"]:last-child { display: none !important; } ```

Thank you, I'll be looking forward to it!