Closed Bug 1546103 Opened 5 years ago Closed 5 years ago

Delay before text entry on Facebook and Twitter

Categories

(Core :: DOM: Navigation, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla68
Tracking Status
firefox-esr60 --- unaffected
firefox67 --- unaffected
firefox68 --- fixed

People

(Reporter: mccr8, Assigned: emilio)

References

(Regression)

Details

(Keywords: regression)

In the last day or so, I've noticed that it takes literally around 10 seconds before I can enter text in a comment on Facebook. The "What's on your mind?" box at the top seems to more or less work, but the "Write a comment..." text entry box that follows somebody's post on the main Facebook feed page takes about 10 seconds before I can type anything into it. Sometimes it seems to take longer.

Text entry on Twitter also seems to be messed up, but the symptom is a little different. I can interact with the text box, but the preexisting prompt text in the box doesn't go away. I don't know if it is the same issue or not.

Keywords: regression

The symptoms sound similar to bug 1539366, but I only noticed this in the last day or two.

I took this profile, but I can't see anything interesting after what looks like the initial page load:
https://profiler.firefox.com/public/6af10a112a216a7f4e707c469f2a83db9e1421a8/calltree/?profileName=&published&v=3

I used mozregression on my Twitter STR, and ended up with this regression range, containing one bug: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=b97df75c9365a162675d962354083af7b5fb40b9&tochange=98adabf295d0bdd1d48cf715fb8ac8ea4ead8766

Looks like there are some other bugs marked as regressions, so maybe it is a dupe.

Component: Untriaged → Document Navigation
Product: Firefox → Core
Regressed by: 1542415
Summary: Delay before text entry on Facebook → Delay before text entry on Facebook and Twitter

Flipping the pref fission.rebuild_frameloaders_on_remoteness_change back to false fixes the issue on both Facebook and Twitter in my regular profile.

Flags: needinfo?(kyle)

The Twitter STR I used for mozregression was something like:

  • Go to Twitter. Log in. Dismiss the save your login prompt.
  • Click on the "reply" icon on one of the Tweets.
  • Click on the text entry box, try to type something.

Ok, I managed to repro the twitter issue on nightly with my main profile. With nightly on a clean profile, I can't seem to get it to happen no matter what I try, which seems odd.

The Google caret issue (Bug 1546019) seems to be happening 100% of the time.

I'm gonna guess there's something with focus and caret/editor that's a problem across all of these bugs, but not duping them against each other quite yet.

Assignee: nobody → kyle
Flags: needinfo?(kyle)

Kyle, I believe this is fixed now, right? Should this be closed?

Flags: needinfo?(kyle)

Fixed via Bug 1546019

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(kyle)
Resolution: --- → FIXED
Assignee: kyle → emilio
Depends on: 1546019
Target Milestone: --- → mozilla68
Has Regression Range: --- → yes
You need to log in before you can comment on or make changes to this bug.