![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
new HTML5 tags for Details and Summary on Dreamwidth
2022-Nov-06, Sunday 11:00 amI've been intending to mention this detail on a slow day... which I guess is today.
Dreamwidth now supports some new HTML5 tags, <details> and <summary>. I know the site-specific <cut> tag breaks RSS and indentations, so I may train myself into a new habit of using this pair instead.
Here goes a test:
Test #1 (using the cut icon in the gui editor)
( Read more under the CUT tag... )
Test #2 (hand written in the HTML editor)
This test text uses the DETAILS tag
CONFIRMED: The CUT hides text from my RSS feed, but the DETAILS/SUMMARY pair do not hide it.
Test #3 (new tags with indentation)
CONFIRMED: The DETAILS/SUMMARY pair do not break indentation. This is useful. :) Although the Dreamwidth gui editor forced in the "open" parameter, which eliminates the benefit of the DETAILS tag in the first place. That's not useful. :( But I can remove it manually within the HTML editor and Save directly there, then it uses default behavior again. Janky, but still useful. :)
Dreamwidth now supports some new HTML5 tags, <details> and <summary>. I know the site-specific <cut> tag breaks RSS and indentations, so I may train myself into a new habit of using this pair instead.
Here goes a test:
Test #1 (using the cut icon in the gui editor)
( Read more under the CUT tag... )
Test #2 (hand written in the HTML editor)
Read this SUMMARY tag, then open to read more under the DETAILS tag...
This test text uses the DETAILS tag
CONFIRMED: The CUT hides text from my RSS feed, but the DETAILS/SUMMARY pair do not hide it.
Test #3 (new tags with indentation)
Read more with indentation...
Something with normal indentation.This text is indented.
CONFIRMED: The DETAILS/SUMMARY pair do not break indentation. This is useful. :) Although the Dreamwidth gui editor forced in the "open" parameter, which eliminates the benefit of the DETAILS tag in the first place. That's not useful. :( But I can remove it manually within the HTML editor and Save directly there, then it uses default behavior again. Janky, but still useful. :)