Re^3: Adding details with summary html tags

in reply to Re^2: Adding details with summary html tags
in thread Adding details with summary html tags

My concern is usability and return of investment.

Why are you expecting users to learn two new intertwined markups while you yourself were already ignoring the spoiler tag?

I'm afraid in the end this will cost more time to implement than time invested applying it.

As I said i'm in favour of adding an automatic JS toggle to long code sections and shortening them by default if they exceed a certain limit.

No one will need to learn new markup and everybody could adjust it to his taste in the display settings.

Same with overly wide code, btw.

Edit: Alone the spared considerations to edit those posts will help justify the investment.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery}

Comment on Re^3: Adding details with summary html tags

Replies are listed 'Best First'.
Re^4: Adding details with summary html tags by Lady_Aleena (Priest) on May 23, 2020 at 19:50 UTC
I have my reasons for ignoring the spoiler tag. I don't believe in spoiler warnings, they are redundant on the web. Everything one reads, hears, and watches on the web comes with an automatic spoiler warning. (I quit Twitter for nearly a year only to have the end of the battle on Avengers: Endgame spoiled by watching the wrong YouTube video.) It is not valid html. (Yes, I know `<readmore>` isn't either.) There is a way to make it so that people won't have to learn a new tag, and I can still have `<details>`. How about instead of using a `<div>`, `<span>`, or `<table>` with a `<td>` with the class of `spoiler` to make the spoiler tag, use the details tag instead with `<spoiler>` having `Spoiler` as the default `<summary`? `<readmore>` could use `<details>` also. Another thing that would need to be changed is `<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">` to `<!DOCTYPE html>`. I did not realize that asking for this would cause this much discussion. I did not think this would be a controversial idea. My OS is Debian 10 (Buster); my perl version is 5.28.1. *No matter how hysterical I get, my problems are not time sensitive. So, relax, have a cookie, and a very nice day!* Lady Aleena	[reply] [d/l] [select]
Re^5: Adding details with summary html tags by LanX (Saint) on May 23, 2020 at 20:32 UTC
> I did not realize that asking for this would cause this much discussion. I did not think this would be a controversial idea. It's not controversial, but very expensive. That's why it needs to be discussed properly. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply]
Re^5: Adding details with summary html tags by LanX (Saint) on May 23, 2020 at 21:31 UTC
> It is not valid html. (Yes, I know `<readmore>` isn't either.) You seem to believe PM is allowing you to use HTML to compose nodes directly. But in reality it's not less an artificial board-markup than BB-code is, just with far less of a learning curve for people knowing (old) HTML. It's a markup which is stored raw in a database and for display it's filtered and rendered into (more or less) "valid" HTML. Our options to deprecate old approved PM-markup are very tiny. It's our data-format, an XML dialect if you want. (just click on XML in the header to see how it looks like) It's in use for 20 years already and old posts still need to be rendered. You mentioned in another post that `<font>` might become deprecated and not displayable. That's not really an issue, because in that case we can still change the renderer to translate `<font>` to valid `<span>` , pretty much the same way we translate `<c>` tags into `<code>` tags. Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply] [d/l] [select]
Re^5: Adding details with summary html tags by marto (Cardinal) on May 23, 2020 at 20:28 UTC
"Everything one reads, hears, and watches on the web comes with an automatic spoiler warning." Simply nonsense. Who enforces this, some secret cyber spoiler police? Please. "Another thing that would need to be changed is `<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">` to `<!DOCTYPE html>`." The site does not generate HTML5, simply changing the doctype declaration will not address this.	[reply] [d/l] [select]

In Section Perl Monks Discussion