Andrew Lee wrote:Finally figured out what's wrong! Fixed.
Thanks for that.
But compact view is still not compact enough -- e.g., UnxUtils entry shows a long list of "Included tools" that pushes any other entry off the viewport.
Andrew Lee wrote:Finally figured out what's wrong! Fixed.
Compact view will leave only the description while hiding all other text eg. extraction instructions etc. If the description itself is long, as is the case with all of vevy's entries that are collections, which is what you are seeing.
I did some research just now, and surprisingly I discovered that CTRL-F doesn't gel well with hidden divs/spans and details/summary, which are the 2 main methods used to implement spoilers. Basically, there is no good way to get the browser to auto-expand and highlight search keywords from within hidden text. I suddenly realize why sometimes when I look for a keyword on a webpage, some matches don't display the highlighted keyword at all, leaving me quite puzzled. As far as I can tell, this is a browser level issue and not something you can work around with code, at least not in a cross-platform, cross-browser way.vevy wrote: ↑Thu Nov 12, 2020 2:22 am The issue is that a spoiler is a problem with CTRL+F and doesn't auto-expand when a highlighted search result is within.
There are a couple of solutions, but it depends on Andrew:
- Auto-expand spoiler if there is a search match inside. This doesn't help with CTRL+F.
- A button to expand all spoilers on page.
- A separate field for "Included tools" that can be among those hidden in compact view.
There is a CSS+JavaScript feature in development to allow this: https://github.com/WICG/display-locking ... tchable.mdAndrew Lee wrote: ↑Thu Nov 12, 2020 5:08 am I did some research just now, and surprisingly I discovered that CTRL-F doesn't gel well with hidden divs/spans and details/summary, which are the 2 main methods used to implement spoilers. Basically, there is no good way to get the browser to auto-expand and highlight search keywords from within hidden text. I suddenly realize why sometimes when I look for a keyword on a webpage, some matches don't display the highlighted keyword at all, leaving me quite puzzled. As far as I can tell, this is a browser level issue and not something you can work around with code, at least not in a cross-platform, cross-browser way.
It won't be hidden in this case. It will depend on the user's preference: always shown with regular (unless in an explicit spoiler) or hidden (with the other fields) in compact view.Andrew Lee wrote: ↑Thu Nov 12, 2020 5:08 am A separate field for included tools also doesn't solve the same issue if what you are looking for is inside the hidden text.
Maybe call it something like "Expand all fields". I think its effect would be quite obvious. You can also add explanatory text on mouse hover or a link to FAQ.A button to expand all spoilers is a possible workaround, but 1) you would need to know that the button exists, and 2) you would need to know _why_ it exists. Otherwise, the user will be left equally puzzled.
I think this would kill the point of spoilers. A choice between two extremes.Or maybe we can have the full view automatically expands all spoilers, while the compact view hides them by default.
Andrew Lee wrote: ↑Take a look and lemme know what you think.
Do you have any opinion as to the best way to tackle this issue now?SYSTEM wrote: ↑Thu Nov 12, 2020 5:17 am There is a CSS+JavaScript feature in development to allow this: https://github.com/WICG/display-locking ... tchable.md
It's not yet supported by any browser, though (only Chromium-based browsers have an implementation, and even in them it's disabled by default).
No, I don't.Andrew Lee wrote: ↑Thu Nov 12, 2020 10:30 pmDo you have any opinion as to the best way to tackle this issue now?SYSTEM wrote: ↑Thu Nov 12, 2020 5:17 am There is a CSS+JavaScript feature in development to allow this: https://github.com/WICG/display-locking ... tchable.md
It's not yet supported by any browser, though (only Chromium-based browsers have an implementation, and even in them it's disabled by default).
Andrew Lee wrote:We could simply have a tag in the description that says "everything below this point" can be hidden for brevity.