Subcontainers to not act as [br] breaks
Remove these ads. Join the Worldbuilders Guild
Subcontainers to not act as [br] breaks
User Interface (UI) / User Experience (UX) · Access management (subscribers/authors) · Created by Silenc3e3e
expired
What functionality is missing? What is unsatisfying with the current situation?
When I add a subcontainer on a public article for content that only users with the right tag can see, it displays just fine to public users, formatting how I expect it to. Not showing the data to users without permission to see the information. But when I open the article as a user with access to the information in the subcontainer, the formatting acts as if the subcontainer is a break (br), which is not what I want it to do. If I want a break, I will add it in to the subcontainer.How does this feature request address the current situation?
The request is simply to adjust the subcontainer to not act as a break. If there is concern about retroactively affecting formatting of people's articles, perhaps code the change so that pre-existing articles add the breaks into the subcontainers that already exist.What are other uses for this feature request?
I don't see other specific uses.Follow up
I want to copy "Those2Nerds'"s comment you can see below, as I think it was a great idea/suggestion/insight, and worth highlighting for the developers: "Subcontainers should continue acting like all other containers and create a <div> in the HTML. A better solution than changing this behavior would be to add a subsection that acts as a <span>. That would address the original request while staying in line with terminology and leaving existing articles unaffected."
Current score
14/300 Votes · +2203 points
Votes Cast
-
+300
by sithis36
on 2024-09-10 02:36 -
+300
by ss2020
on 2024-09-03 17:02I agree, if we want it to break, we could then control it with our own BBC codes.
-
+1
by Amancham
on 2024-09-03 15:46 -
+300
by Kittymonster
on 2024-08-31 22:09 -
+300
by Maz_Cat
on 2024-08-29 17:51 -
+1
by Pete Nelson
on 2024-08-29 17:21I haven't tested it, but I suspect you can accomplish this already with some CSS.
-
-1
by PoppaeaSabina
on 2024-08-29 14:32I would prefer Rin's suggestion. I really do feel it could break things for a lot of people to do it the way suggested. Otherwise, no objections.
-
+300
by CrocOsnake
on 2024-08-29 01:34 -
+1
by DesNordlund
on 2024-08-28 21:10 -
+1
by WeStanNikolai
on 2024-08-28 15:12 -
+100
-
+100
-
+100
by Mahdi Avendesora
on 2024-08-27 12:57 -
+100
by Those2Nerds
on 2024-08-27 12:54Subcontainers should continue acting like all other containers and create a <div> in the HTML. A better solution than changing this behavior would be to add a subsection that acts as a <span>. That would address the original request while staying in line with terminology and leaving existing articles unaffected.
-
+300
by Silenc3e3e
on 2024-08-27 09:47
Find your way!
Resources
WHO WE ARE
LEGAL
Get the news
Listen to our Podcast
Our Allies
by 3 Armored Kittens · Prodromos v.1.1 - World Anvil 0.9.15.029 © 2017-2024 [en] | Anvil Time: 02:01, Sep 19 2024