[pl] menu reference: "Report Web Forgery" is before "Report Broken Website"

VERIFIED FIXED

Status

--
minor
VERIFIED FIXED
12 years ago
12 years ago

People

(Reporter: marcoos, Assigned: marcoos)

Tracking

({fixed1.8.1.1, verified1.8.1.1})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments, 1 obsolete attachment)

(Assignee)

Description

12 years ago
As in en-US in bug 353388, firebird-toc.rdf and menu_reference.xhtml needs a little reordering.

This is branch only, already fixed on trunk.
(Assignee)

Comment 1

12 years ago
Created attachment 239903 [details] [diff] [review]
move "Report Web Forgery" to the right place in the document

Requesting approval1.8.1. 

It'd be nice to have in RC2, though it's a minor issue.
Attachment #239903 - Flags: approval1.8.1?
(Assignee)

Updated

12 years ago
Blocks: 350040
(Assignee)

Updated

12 years ago
Blocks: 353388
(Assignee)

Updated

12 years ago
No longer blocks: 353388
Depends on: 353388

Comment 2

12 years ago
Comment on attachment 239903 [details] [diff] [review]
move "Report Web Forgery" to the right place in the document

[pl] reporter-reordering in help approved for RC2
Attachment #239903 - Flags: approval1.8.1? → approval1.8.1+
(Assignee)

Comment 3

12 years ago
Checked in, fixed.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED
(Assignee)

Comment 4

12 years ago
The "fix" in the en-US bug has been backed out. 

Per Pike's post in .l10n, we'll fix it for 2.0.0.1.

Just great. :(
Status: RESOLVED → REOPENED
Resolution: FIXED → ---

Comment 5

12 years ago
Should we remove the blocking on bug 350040, then?

Adding fixed1.8.1 keyword to move this off the radar of stuff that needs work 'til 2.0.
Keywords: fixed1.8.1
(Assignee)

Comment 6

12 years ago
Yup.
No longer blocks: 350040
(Assignee)

Comment 7

12 years ago
Created attachment 244463 [details] [diff] [review]
Revert the previous patch for 2.0.0.1+
Attachment #244463 - Flags: approval1.8.1.1?
(Assignee)

Updated

12 years ago
Whiteboard: [needs "unfixing" for 1.8.1.1]

Comment 8

12 years ago
Comment on attachment 244463 [details] [diff] [review]
Revert the previous patch for 2.0.0.1+

marcoos, did you check that the whitespace/newline change in firebird-toc.rdf works? I'm not sure how whitespace tolerant xml is at that point. It at least sure looks like an odd point to break the line.
Attachment #244463 - Flags: review?(marcoos+bmo)
(Assignee)

Comment 9

12 years ago
Created attachment 244813 [details] [diff] [review]
Revert the previous patch for 2.0.0.1+

Attachment 244463 [details] [diff] is just basically the oposite of attachment 239903 [details] [diff] [review] (+bumping the date up). We had that line break in beta 2 and it worked.

But I agree that it's a bit confusing, so I made a new patch.
Attachment #244463 - Attachment is obsolete: true
Attachment #244813 - Flags: approval1.8.1.1?
Attachment #244463 - Flags: review?(marcoos+bmo)
Attachment #244463 - Flags: approval1.8.1.1?

Comment 10

12 years ago
Comment on attachment 244813 [details] [diff] [review]
Revert the previous patch for 2.0.0.1+

Yep, please use the fixed1.8.1.1 and verified1.8.1.1 keywords to track landing and testing of this fix.
Attachment #244813 - Flags: approval1.8.1.1? → approval1.8.1.1+
(Assignee)

Updated

12 years ago
Keywords: fixed1.8.1 → fixed1.8.1.1
Whiteboard: [needs "unfixing" for 1.8.1.1]
(Assignee)

Updated

12 years ago
Status: REOPENED → RESOLVED
Last Resolved: 12 years ago12 years ago
Resolution: --- → FIXED
(Assignee)

Comment 11

12 years ago
verified with Mozilla/5.0 (Windows; U; Windows NT 5.1; pl; rv:1.8.1) Gecko/2006110603 BonEcho/2.0
Status: RESOLVED → VERIFIED
Keywords: verified1.8.1.1
You need to log in before you can comment on or make changes to this bug.