Skip to main content
I
InfiniteVoid
Participant
May 4, 2010
Question

HtmlExporter missing strikethrough condition

  • May 4, 2010
  • 1 reply
  • 829 views

Hi there,

I had discover a bug(?) or unintended feature - able to do strikethrough on TextFlow but when use TextConverter to convert to html tag. The <S></S> tag is missing. After some digging through the sdk code and found out HtmlExporter doesn't handle the condition of strikethrough. My current sdk version 4.0.0.14159 (come with flex builder 4)

Tried version 4.1.0.14756, it seems to be the same.

Search through the change log - couldn't find anything related to this on latest build.

Question about this,

Is it a bug? or is it intended? If it is intended, will I get any similar feature in the future build?

Unrelated question,

All the html tag generate by the HtmlExporter are deprecated in html 4. Is there any plan to move forward to use CSS?

I can try to hack around to get it to work for my environment but I just don't want to make a lot of changes if there is new sdk that fix it in the future. Please let me know what I can do with this.

Cheers

This topic has been closed for replies.

1 reply

R
Adobe Employee
rdermer
Adobe Employee
May 4, 2010

TLF HTML importer is for compatibility with TextField HTML import/export.  Its intended for interchange with TextField.  That's why the TextConvertor constant is named TEXT_FIELD_HTML_FORMAT.

TextField.htmlImport doesn't document that it supports the <s> tag.  We could still add it to tlf's importer/exporter.  I'll get a bug added.

An html importer would be a separate piece of work.

Richard

I
InfiniteVoidAuthor
Participant
May 4, 2010

If the textflow allows the strikethrough format, I don't see the reason not to have it in html importer/exporter. If html doesn't support strikethrough, then we have nothing much that we can do but no, html does support strikethrough, therefore I don't see any reason the feature is missing.

I'm going to temporary disable this feature for my custom richtext editor until further notice of this feature implemented. It just looks awkward with a richtext editor without strikethrough though.

-----

Other than the strikethrough, would someone be able to tell me what is the direction of the html importer/exporter in the future? Because the current importer/exporter is using the deprecated html tag. Would there be a possibility of moving to CSS?

B
bvl
Known Participant
May 5, 2010

After diving into the docs and the code it becomes clear that TLF wasn't build with the goal of becoming a standards compliant HTML/CSS renderer. I think it's safe te assume that this will stay that way for at least a few years.

The importers/exporters are somewhat useful but even if you extend them they only provide a piece of the puzzle, e.g. in CSS you often use unit types that are relative to some other (already earlier) computed value. TLF wouldn't understand those unit type nor would it know what to do with it, e.g. em values or gr (grid) units and it doesn't give the developer a hook/event to solve those custom computings before using them. If you are happy to extend a lot of related classes and don't shy a way from some hackerish stuff then there are options to get the results you want but those require a lot of time and will probably break with the next TLF release. And of course you would still want to leverage the TLF SWZ (the TLF lib ending up in your users Flash Player cache) with a minimum extra download for your extensions.

So that doesn't mean that TLF can't be used as the basis of a more HTML/CSS standards compliant renderer/editor but I think it's most likely that these kind of efforts will come from third party developers either from the open source community (e.g. tlfx) or from commercial parties.

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