Closed Bug 1604395 Opened 4 years ago Closed 4 years ago

Dead assignment in ContentEventHandler::AppendFontRanges

Categories

(Core :: DOM: Events, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla73
Tracking Status
firefox73 --- fixed

People

(Reporter: alexhenrie24, Assigned: alexhenrie24)

Details

Attachments

(1 file)

ContentEventHandler::AppendFontRanges currently looks like this:

if (startXPOffset > lastXPEndOffset) {
  // Create range for skipped leading chars.
  AppendFontRange(aFontRanges, baseOffset);
  baseOffset += GetTextLengthInRange(aContent, lastXPEndOffset,
                                     startXPOffset, aLineBreakType);
  lastXPEndOffset = startXPOffset;
}

FontRange* fontRange = AppendFontRange(aFontRanges, baseOffset);
fontRange->mFontName.Append(NS_ConvertUTF8toUTF16(font->GetName()));
fontRange->mFontSize = font->GetAdjustedSize();

// The converted original offset may exceed the range,
// hence we need to clamp it.
uint32_t endXPOffset =
    iter.ConvertSkippedToOriginal(runIter.GetStringEnd());
endXPOffset = std::min(frameXPEnd, endXPOffset);
baseOffset += GetTextLengthInRange(aContent, startXPOffset, endXPOffset,
                                   aLineBreakType);

There is no reason to set lastXPEndOffset to startXPOffset because it is overwritten again before it is used. This assignment has been a dead assignment ever since it was added in January 2015 as part of the fix for Bug 569334.

Assignee: nobody → alexhenrie24
Status: NEW → ASSIGNED
Pushed by rmaries@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/78b4443ee620
Remove dead assignment from ContentEventHandler::AppendFontRanges. r=masayuki
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla73
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: