Closed Bug 1182969 Opened 10 years ago Closed 10 years ago

Use nsTHashTable::Iterator in accessible/

Categories

(Core :: Disability Access APIs, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla42
Tracking Status
firefox42 --- fixed

People

(Reporter: n.nethercote, Assigned: n.nethercote)

References

Details

Attachments

(2 files)

Because iterators are so much nicer than enumerate functions. There are two occurrences of EnumerateEntries() in accessible/ to be dealt with.
Attachment #8637654 - Flags: review?(tbsaunde+mozbugs)
Assignee: nobody → n.nethercote
Status: NEW → ASSIGNED
Here's a |diff -w| version of the patch that is a lot easier to read.
Comment on attachment 8637654 [details] [diff] [review] Use nsTHashTable::Iterator in accessible/ thanks, I'm swamped with a11y e10s so don't have time for cleaning stuff up :/ > // Process rendered text change notifications. >- mTextHash.EnumerateEntries(TextEnumerator, mDocument); >+ ProcessRenderedTextChangeNotifications(); > mTextHash.Clear(); it might make more sense for that to be part of ProcessRenderedText, but up to you.
Attachment #8637654 - Flags: review?(tbsaunde+mozbugs) → review+
Thank you for the fast review. > it might make more sense for that to be part of ProcessRenderedText, but up > to you. In this case I left it as a separate function because the loop body was large, but I'm happy to inline it and will do so.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla42
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: