Closed Bug 613437 Opened 15 years ago Closed 15 years ago

Investigate the recent BrowserScope Richtext2 regression on mozilla-central

Categories

(Core :: DOM: Editor, defect)

Product:
Core
Component:
DOM: Editor
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: ehsan.akhgari, Assigned: ehsan.akhgari)

References

(
URL
)

Details

(Whiteboard: [browserscope])

Yesterday's nightly scores 580 on the richtext2 suite. Today's nightly scores 542. Here is the regression range: <http://hg.mozilla.org/mozilla-central/pushloghtml?tochange=7e42ccaa7269&fromchange=ad227939db82> Nothing in the regression range is editor related. I'm bisecting this range to find the culprit.
Specifically, we've lost 38 points in the selection subset in that suite. Nothing in that range jumps out at me as selection related though.
This is also caused by something in the TM merge. hg bisect however always terminates on the merge changeset, so I wasn't really able to track it down correctly. :(
Depends on: 613960
I'm getting 580 on my TM and m-c builds...
Hmm, yes, the regression seems to have been fixed...
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.