Introduction
The <details> tag provides a convenient way to create collapsible content, improving the readability of posts. However, in practice, it has several limitations, especially within Hive posts.
Background & Basics
The <details> element is an HTML tag that allows content to be displayed only when needed.
Common use cases include spoilers, additional explanations, or optional information.
Markdown does not natively support this element, so it often does not render correctly in pure Markdown editors.
Identified Limitations
1. Lack of Markdown Support
- Many Hive editors rely on Markdown, which leads to
<details>tags not being interpreted correctly.
2. Rendering Issues in Different Frontends
- On PeakD, the
<details>tag functions correctly. - On Hive.blog, the
<details>tag is supported, but the selection box is misaligned to the right, creating a visual issue. - On Ecency, the text within
<details>is displayed directly instead of being hidden, making it ineffective as a collapsible section. - On mobile displays, some Hive apps do not render
<details>properly, leading to inconsistent behavior.
3. Limited Styling Options
The styling of <summary> and <details> cannot be easily modified using Markdown or CSS.
Icons or images inside <summary> are sometimes displayed incorrectly.
4. No Dynamic Text Change
The <summary> element remains static; switching between "Show details" and "Hide details" does not work without JavaScript.
JavaScript is not supported in Hive posts.
Possible Workarounds
Using Pure Markdown: Instead of <details>, manual spoiler or collapsible text formatting can be used.
External Links: If the content is too extensive, an external link to a fully functional page can be provided.
Testing Hive Frontends: If <details> must be used, it should be tested on different frontends beforehand.
Relevance to Hive & Web3
A consistent display of <details> tags across all Hive frontends would be desirable.
Web3 applications require standardized methods for rendering interactive content without JavaScript.
Conclusion
The <details> tag is a useful feature for structuring content, but it has some limitations when used in Hive posts. Users should be aware that not all frontends support it correctly and should consider alternative solutions.
Additional Resources
- HTML Specification –
<details> - Can I use – Browser Support für
<details> - Stack Overflow – Probleme mit
<details>in verschiedenen Umgebungen
This wiki article is based on a problem that I analyzed and worked out together with artificial intelligence. The content was created with the support of AI and then checked manually to ensure high quality and accuracy.
Hello.
There is reasonable evidence that this article is machine-generated.
We would appreciate it if you could avoid publishing AI-generated content (full or partial texts, art, etc.).
Thank you.
Guide: AI-Generated Content = Not Original Content
Hive Guide: Hive 101
If you believe this comment is in error, please contact us in #appeals in Discord
Hi @hivewatchers, the post was actually generated by AI. I am just showing with the post what is possible with AI today. But it also shows me that my idea of generating articles for a wiki in which I discuss a problem from my daily work with AI is not a good idea. Why is that? Don't you also want to make Hive a good port?
Hi.
As explained in our guide, could you please set rewards to be declined and clearly inform in that content that it is AI-generated.
Thanks for your feedback @hivewatchers. I have created several articles with AI. Unfortunately, I only remembered to decline the rewards for two publications. Unfortunately, this is no longer possible in retrospect. Another mistake was that I didn't clearly declare it as AI, which I have now made up for afterwards. I certainly didn't want to violate any guidelines. Rather, I wanted to test the extent to which AI is able to create simple structured content for wiki articles. It's not about creativity, but about emotionless content without personal opinions. I think AI can be used wonderfully for such things today. If you like, you can read my post on my main account @vanje. There I described what test I did and with what intention. I would also like to mention that I support their action and will continue to do so, even though I am regularly downvoted by endhivewatchers. I hope I didn't end up on the blacklist.
Edit: I have given it some more thought. First of all, I adapted the prompt for creating wiki articles so that a note appears at the end of a post to indicate that the wiki article was created with AI and checked manually. However, I see a problem in the motivation of potential article creators. If I tell them that they should refuse a reward, they probably won't make the effort. Perhaps it would actually be better not to pursue the project any further?
I would recommend clearly mentioning that the post is AI-generated in the title of the post.