Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Article title formatting in Write > HTML view #696

Closed
petecooper opened this issue May 26, 2016 · 4 comments
Closed

Article title formatting in Write > HTML view #696

petecooper opened this issue May 26, 2016 · 4 comments

Comments

@petecooper
Copy link
Member

Background: http://forum.textpattern.com/viewtopic.php?id=47043

STR: draft an article with a title. Body and excerpt are optional. View article via Write > HTML tab. Title is not HTML-formatted, whereas body and excerpt are.

safariscreensnapz001

UX is somewhat misleading in that respect. Some potential solutions outlined in OP linked above.

@petecooper petecooper changed the title Title formatting in Write > HTML view Article title formatting in Write > HTML view May 26, 2016
@philwareham
Copy link
Member

philwareham commented May 26, 2016

Thinking about it, the title content field does not contain any enforced HTML tags (a user would manually create whatever wrapping tags themselves), whereas the body and excerpt do (as they are fully Textile formatted).

So in this regard, it is correct in it's current layout.

@phiw13
Copy link

phiw13 commented May 26, 2016

But the title field can eventually have characters converted to entities - which you may want to see. Example, type: I'am in the title field, which is converted to I'am.

(and oddly in the body field, you get I’am - one of the two is wrong, but that is meat for another issue)

(yes, intentional mistake in that snippet!)

@philwareham
Copy link
Member

@phiw13 Hmmm, good point. I don't know how to convert this to HTML or fix the other issue you mention, so maybe @Bloke or @bloatware can help?

@petecooper
Copy link
Member Author

I'm going to close this issue as it's as-designed and the issue @phiw13 mentions is outlined in #697

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants