Closed
Bug 609164
Opened 14 years ago
Closed 13 years ago
We should retain user formatting (line breaks) for privacy policy and EULA
Categories
(addons.mozilla.org Graveyard :: Public Pages, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
5.12.12
People
(Reporter: krupa.mozbugs, Assigned: gkoberger)
References
()
Details
(Whiteboard: [z][qa!])
Attachments
(1 file)
490.18 KB,
image/png
|
Details |
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.12) Gecko/20101026 Firefox/3.6.12 steps to reproduce: 1. Add three paragraphs of content(formatted with spacing and what not) as privacy policy/EULA to some add-on. 2. Navigate to the privacy policy page- https://addons.allizom.org/z/en-US/firefox/addon/182409/privacy/ and EULA page- https://addons.allizom.org/z/en-US/firefox/addon/182409/eula/92421?src=addondetail expected result: User formatting is retained without the user having to use html actual result: All user formatting is lost. Also: We save user formatting on custom license- https://addons.allizom.org/z/en-US/firefox/addon/182409/license/20100621
Updated•14 years ago
|
Target Milestone: 5.12.3 → 5.12.4
Comment 1•14 years ago
|
||
Yeah, I recently updated my privacy policy for Flagfox and it's all one giant blob that's kind of a mess. (on production server) (In reply to comment #0) > User formatting is retained without the user having to use html I don't think HTML is allowed here. At least it says it doesn't.
Updated•14 years ago
|
Target Milestone: 5.12.4 → 5.12.7
Comment 2•14 years ago
|
||
What's the ETA on getting someone to fix this? I should be a quick fix (I hope) and as of right now my current privacy policy is hard to read because of this. I make a point of trying to handle privacy correctly and have my new policy divided into 4 sections that are all smushed together right now. https://addons.allizom.org/en-US/firefox/addon/flagfox/privacy/ (I'm sticking a link to it in the URL field because the current one is 404) By the way, this bug isn't "[ddn]" (design decision needed) as the line breaks are clearly saved and shown correctly when editing in the developer hub. They're just not respected when showing on the public page. https://addons.allizom.org/en-US/developers/addon/edit/5791/descriptions
Whiteboard: [z][ddn] → [z]
Updated•14 years ago
|
Summary: We should retain user formatting for privacy policy/ EULA → We should retain user formatting (line breaks) for privacy policy and EULA
Comment 3•14 years ago
|
||
(In reply to comment #2) > What's the ETA on getting someone to fix this? I should be a quick fix (I hope) It's schedule for the next milestone. 5.12.6 freezes on friday, 5.12.7 is next. See https://mail.mozilla.com/home/wclouser@mozilla.com/AMO%20Schedule.html
Comment 4•14 years ago
|
||
(In reply to comment #3) This bug has had its target milestone bumped up twice, totaling 4 milestones. Until someone is assigned this bug, unfortunately, the milestone means nothing.
Comment 5•14 years ago
|
||
(In reply to comment #4) > (In reply to comment #3) > This bug has had its target milestone bumped up twice, totaling 4 milestones. > Until someone is assigned this bug, unfortunately, the milestone means nothing. ><
Target Milestone: 5.12.7 → Q1 2011
Updated•14 years ago
|
Priority: -- → P3
Updated•13 years ago
|
Assignee: nobody → gkoberger
Target Milestone: Q1 2011 → 5.12.11
Comment 6•13 years ago
|
||
qa: Make sure we don't lose any content when saving strings that allow html formatting.
Whiteboard: [z] → [z][qa!]
Updated•13 years ago
|
Flags: in-testsuite?
Flags: in-litmus?
Assignee | ||
Comment 7•13 years ago
|
||
QA: The goal is to get the output as close to what the user enters as possible- it's supposed to strip out excessive newlines where they shouldn't be. Make sure you test with lots of HTML- specifically, block level elements (<ul>, <li>, <blockquote>, etc). Also watch for HTML attributes and unicode. Feel free to ask me (gkoberger on #amo) if you have any questions. If you need test case ideas, you can get lots of inspiration here: https://github.com/jbalogh/zamboni/commit/f9d8328ad29b14f3d82e060a60811fa6357e7d82#L2R318 Commit: https://github.com/jbalogh/zamboni/commit/f9d8328ad29b14f3d82e060a60811fa6357e7d82
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 8•13 years ago
|
||
moving to 5.12.12, so that it can get some QA.
Target Milestone: 5.12.11 → 5.12.12
Comment 9•13 years ago
|
||
Thank you so much for fixing this. My privacy policy is actually readable now. Verified fixed using: https://addons.allizom.org/en-US/firefox/addon/flagfox/privacy/ See also bug 510381. There's no need for a box to put the privacy policy or EULA text in. The license page doesn't do this and looks much better, makes better usage of available space, and makes it easier to read. For example, my privacy policy could fit on screen all at once, but instead you have to scroll through the little text box to read it.
Status: RESOLVED → VERIFIED
Comment 10•13 years ago
|
||
Also verified fixed for EULA via this URL: https://addons.allizom.org/en-US/firefox/addon/delicious-bookmarks/eula/52958
Comment 11•13 years ago
|
||
I'm just verifying the fix for a bug affecting me. If the QA team needs to do more testing beyond the bug as filed please do so. If there's a lot more to test here a new bug to cover it might make sense, as this one specifically is complete. This general type of bug is a repeating problem that has popped up many times in the past again and again. I wouldn't be surprised if there are other fields where this is also the case again.
Updated•8 years ago
|
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•