Open Bug 1045253 Opened 10 years ago Updated 2 years ago

Cannot focus ContentEditable in different domain during Click event if MouseDown was canceled

Categories

(Core :: DOM: UI Events & Focus Handling, defect)

31 Branch
x86
Windows 8
defect

Tracking

()

UNCONFIRMED

People

(Reporter: MSAOfficeWebApps, Unassigned)

Details

Attachments

(1 file)

Attached file SideBySideRepro.zip
User Agent: Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; Win64; x64; Trident/6.0; .NET4.0E; .NET4.0C; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET CLR 2.0.50727)

Steps to reproduce:

1. Download attached folder and unzip somewhere on a server.
2. Set up two sites.
  a. Site 1: Bound to folder "Source"
  b. Site 2: Bound to folder "Target"
3. Update Source/default.htm so that TargetFrame points to http://site2/target.htm
  - Note: If both sites are configured on localhost with Site 2 being bound to Port 89, no changes are necessary
4. Navigate to http://Site1
5. Click in the ContentEditable within the IFrame for Site 1 (Source)
6. Click in the ContentEditbale within the IFrame for Site 2 (Target)


Actual results:

Focus does not change (usually, once in a while it will), despite the fact that the Click event was still fired and we called focus.

Other notes about reproducibility:
 - Does not repro if both iframes are in the same domain/port.
 - Does not repro if focus is in the parent frame (even if the domain is different from the child)
 - Does not repro if focus is anywhere in the browser chrome
 - Does not repro in other browsers


Expected results:

Focus should move on the ContentEditable in IFrame 2.
Component: Event Handling → User events and focus handling
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: