When launch an app, a selectionstatechanged event (sent from Homescreen process) always comes before Webapps:Launch. The profile from Flame shows it takes ~20ms on B2G main thread: http://people.mozilla.org/~bgirard/cleopatra/#report=a899fb11de4ad4b292f5f2e19b918949ed5041e9&select=1598,1619. I am not sure is the event necessary.

I found that we have 1 selectionstatechanged event with reason blur before app launch. I don't think we have enough information to filter out this useless event. We should able to resolve this issue after refactoring Touch/Selection carets code.

I examine this bug after applying touch/selectioncaret refactor code. And I cannot find this event before app launch. So, let wait refactoring code getting landed and check it again!!

[Tracking Requested - why for this release]:

With the profile [1] today, I can still see it [119236,119283]... Gecko: https://hg.mozilla.org/mozilla-central/rev/1af1b4e1c35a [1] http://people.mozilla.org/~bgirard/cleopatra/#report=9ca00bbd19a1585f5e3cbeb8a624da404ccbc6c4

Yes, we didn't enable accessible caret by default. So this problem still exists. Bug 1172382 will enable it by default. Let's wait!

Bug 1172382 was landed. Can this issue still be reproduced?

(In reply to Ting-Yu Lin [:TYLin] (UTC+8) from comment #6) > Bug 1172382 was landed. Can this issue still be reproduced? Great! I don't see it anymore.