Improper Range creation from caretRangeFromPoint on floated contentEditable regions

Confirmed Issue #4471321 • Assigned to Jose L.


Sep 3, 2015
This issue is public.
Reported by 0 people

Sign in to watch or report this issue.

Steps to reproduce


Repro Steps:

  • Open console
  • (on touch screen) touch on the image with alt text “TinyMCE Logo”
    Expected results:
     * No message saying Edge is weird in the console
  • Edge is weird (how’d we get here) message.

(Edge is returning the text node above the editor as the commonAncestorContainer of the Range returned from caretRangeFromPoint–when the passed-in coordinates are clearly not matching…)


  1. Create two contentEditable elements that contain multiple block level elements that have text nodes.
  2. Apply float left to the contentEditable elements.
  3. Attempt to create Range element from caretRangeFromPoint at an X/Y position that should contain a text node.

Expected Results:

To be able to create a Range element at a given X/Y point and have its commonAncestorContainer be the textNode for the text located at the X/Y point. This textNode’s parent should return the same element as elementFromPoint for the same X/Y point.

Actual Results:

Dev Channel specific:



0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Mara P.”

      Changed Assigned To to “Amit J.”

      Changed Assigned To to “Travis L.”

      Changed Assigned To from “Travis L.” to “Arthur B.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Arthur B.” to “Sergey D.”

      Changed Status from “Confirmed”

      Changed Status to “Confirmed”

      Changed Assigned To from “Sergey D.” to “Eugene V.”

      Changed Steps to Reproduce

      Changed Steps to Reproduce

      Changed Assigned To from “Eugene V.” to “Jose L.”

    You need to sign in to your Microsoft account to add a comment.

    Sign in