Closed Bug 1101897 Opened 10 years ago Closed 10 years ago

"Rows per page" to "Pictures per page"

Categories

(Webtools Graveyard :: Air Mozilla, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: peterbe, Assigned: anuragchaudhury)

References

()

Details

(Whiteboard: [good first bug])

Attachments

(1 file)

On the Picture Gallery view (in management) there's a widget at the bottom that says "Rows per page" but what you're selecting is how many pictures per page.
Whiteboard: [good first bug]
Hi Peter,

I made the change and committed the changes. However, I accidentally made the commit into the existing pull request

https://github.com/mozilla/airmozilla/pull/127

Sorry about that. I'll be more careful next time so as to issue a new pull request.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee: nobody → anuragchaudhury
We changed it so that it affects all places where that snippet is used. On the Picture Gallery we need it to say "Pictures per page" on the Event Manager it needs to say "Rows per page".
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Hey Peter, but they both use _angular_pagesize, so should we add in a function which depending on the parameter passed produces the label as "Rows per page" or "Pictures per page"?
(In reply to Anurag Chaudhury from comment #4)
> Hey Peter, but they both use _angular_pagesize, so should we add in a
> function which depending on the parameter passed produces the label as "Rows
> per page" or "Pictures per page"?

Yeah, we'll using a trick to set an exception outside the inclusion of _angular_pagesize. I actually already have a solution in place. Just haven't merged it yet.
(In reply to Peter Bengtsson [:peterbe] from comment #5)
> (In reply to Anurag Chaudhury from comment #4)
> > Hey Peter, but they both use _angular_pagesize, so should we add in a
> > function which depending on the parameter passed produces the label as "Rows
> > per page" or "Pictures per page"?
> 
> Yeah, we'll using a trick to set an exception outside the inclusion of
> _angular_pagesize. I actually already have a solution in place. Just haven't
> merged it yet.

Oh, I see. In that case, I won't start working on it.
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: