We are migrating CKEditor issue tracking to GitHub. Please, use GitHub to report any new issues.

The former tracking system (this website) will still be available in the read-only mode. All issues reported in the past will still be available publicly and can be referenced.

Important: we decided not to transfer all the tickets to GitHub, as many of them are not reproducible anymore or simply no longer requested by the community.
If the issue you are interested in, can be still reproduced in the latest version of CKEditor, feel free to report it again on GitHub.
At the same time please note that issues reported on this website are still taken into consideration when picking up candidates for next milestones.

To report a new issue, go to https://github.com/ckeditor/ckeditor-dev/issues and follow the instructions in the issue template.

Context Navigation

← Previous Ticket
Next Ticket →

Opened 8 years ago

#16991 new Bug

readyState of iFrame is "interactive" in FireFox 53.0 while "complete" in Chrome 58.0

Reported by:	Sjoerd van Loon	Owned by:
Priority:	Normal	Milestone:
Component:	General	Version:	4.7.0
Keywords:	selenium javascript	Cc:

Description

In our automatic tests we have a part which waits untill all iFrame on the page have readystate "complete". When we introduced the new FireFox, all tests with the CKEditor on them halted because they were interactive. I could reproduce this on your nightly build.

For now we will be building in a work around in our automatic tests.

Steps to reproduce

With Firefox 53.0
Go to your nightly build
Query document.getElementsByTagName("iframe")[0].contentWindow.document.readyState

Expected result

complete

Actual result

interactive

Other details (browser, OS, CKEditor version, installed plugins)

FF 53.0 windows 8.1

Note: See TracTickets for help on using tickets.