Skip to main content
D
dacaglSAS
Known Participant
July 14, 2011
Question

Has DIVELEMENT always created a line break?

  • July 14, 2011
  • 1 reply
  • 594 views

Just wondering if the DIVELEMENT always renders a line break after the ending </div> tag.  That is not what HTML does so I'm just wondering if its a bug or the way DIVELEMENT is supposed to render.  I can't find it documented anywhere so I thought I would run it by folks on the forum.

Here is an example:

<TextFlow xmlns="http://ns.adobe.com/textLayout/2008" version="2.0.0" locale="en">
<div>Concept topic Number 1</div><div>This is some dummy content for flex that has topic type of: concept.</div><div>Note:    This is dummy content, so nothing here is going to be really thought provoking or, shall we say, deep.</div></TextFlow>

and it renders like this, where the div's are seperated by line breaks:

Concept topic Number 1
This is some dummy content for flex that has topic type of: concept.
Note:    This is DAVID's dummy content, so nothing here is going to be really thought provoking or, shall we say, deep.

Thanks!!

This topic has been closed for replies.

1 reply

J
Adobe Employee
Jin-Huang
Adobe Employee
July 15, 2011

<div>Concept topic Number 1</div> means <div><p><span>Concept topic Number 1</span></p></div>, which is by design.

There must be more than one pragraph in div, more than one span in paragraph , span's parent must be a paragraph... ...There are many rules in TLF. Normalization process will create required elements for the users to obey all the rules.

D
dacaglSASAuthor
Known Participant
July 15, 2011

Thank you Jin!

The fact that the "<div>" is actually rendered as "<div><p><span>" does sound familiar now.  Thanks!

I do have some questions about the rules you stated...

There must be more than one pragraph in div, more than one span in paragraph , span's parent must be a paragraph... ...There are many rules in TLF. Normalization process will create required elements for the users to obey all the rules.

Are these rules written anywhere?  We have been struggling for days trying to write a XSD schema that conforms to the TLF 2.0 specification since one doesn't exist already.  If these rules are not in the spec. then the spec. needs to be updated.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices