Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Drag and drop page inspector to cross-origin iframes in chrome and Edge Chromium does not work - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Drag and drop page inspector to cross-origin iframes in chrome and Edge Chromium does not work
KB0815486

Drag and drop page inspector to cross-origin iframes in chrome and Edge Chromium does not work


661 Views Last updated : Oct 31, 2022 public Copy Permalink
KB Summary by Now Assist

Description

The page inspector does nothing when its crosshairs are dragged and then dropped onto an iframe, an external site embedded in the local site's UI. This issue only occurs with some Chrome and Edge Chromium browsers.

Steps to Reproduce

1. Launch instance with Chrome browser.
2. Click on System settings > Developer, Enable Automated Test Framework Page Inspector.
3. Create a UI Page with cross origin iframes, click on Try it.
4. Attempt to drag and drop the page inspector to cross-origin iframes.

Workaround

This is a browser manufacturer limitation and not a SN issue. Any cross-origin iframes are external sites embedded within the platform UI. The defect expects the Page Inspector to alert the user to the lack of support, and instead does nothing on some browser types. The missing notification would only alert the user that they cannot test an external site with the ATF. ATF will not allow testing external sites anyway.


Related Problem: PRB1388202

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.