all <li> tags "polutted" with '≫' globally
See original GitHub issueDescribe the bug
when I render arwes, all <li> nodes in the document get an li:::before
node with content ‘≫’.
To reproduce
render arwes in a DOM tree containing lists
Expected behavior
don’t affect DOM elements outside arwes
- Packages version: 1.0.0-alpha.18
- Node.js 15.11 NPM 7.7.6
- OS: windows
Testing environment
chrome latest on windows
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
<li>: The List Item element - HTML: HyperText Markup Language
The HTML element is used to represent an item in a list. ... This element includes the global attributes. value.
Read more >HTML li tag - W3Schools
The <li> tag is used inside ordered lists(<ol>), unordered lists (<ul>), and in menu lists ... The <li> tag also supports the Global...
Read more >A Review of a Class of Emerging Contaminants - NCBI
With the recognition of organic pollutants, bromine-based flame retardants have been banned worldwide due to their environmental persistence, ...
Read more >Spatial distribution and level of contamination of potentially ...
The environmental behaviour of potentially toxic elements in soil and sediments is critically dependent on several factors as their content, ...
Read more >BeautifulSoup - Find all <li> in <ul> - GeeksforGeeks
Below the code, the HTML snippet contains a body with ul and li tags that have been obtained by the beautifulsoup object.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Fixed in https://github.com/arwes/arwes/commit/9d480a3d1f9a8c0629ff8c05a59401e2a000b1a0.
Input/Textarea components will be handled in #112.
@amir-arad , the form elements will be covered later in the roadmap. So yes, there are many details and components to create about that. Thank you for reporting them 😉