Qunit-fixture css overrides no longer producing desired result as of qunit 2.14?
See original GitHub issueHi,
It seems as though this change that landed in qunit 2.14 has altered the assumptions that ember-qunit uses when attempting to affect the placement of the testing container by overriding the css on #qunit-fixture
. Now that qunit marks #qunit
as position: fixed
the container has shifted up to the top of the window and occludes the menu:
qunit 2.14
And the expected behavior (shown using qunit 2.13)
It seems like this is probably related to #793 but is concerned with the actual visual layout instead of underlying test failures.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
How to change css option of DOM element inside the Qunit ...
I try to create unit test for resize() method using QUnit. Here is my QUnit fixture: <div id="qunit-fixture"> <table cellspacing="0" ...
Read more >Directed Test Generation and Analysis for Web Applications
Generating Fixtures for JavaScript Unit Testing [127]: A. Milani Fard, ... discovering more state does not necessarily result in higher ...
Read more >Testing of mobile HTML5 Web-Applications
be moved to the client side and only the results are sent to the server. This allows to use the application even if...
Read more >Learning jQuery - Fourth Edition
alone in the document header, it will have no effect. JavaScript code is generally run as soon as it is encountered in the...
Read more >Full text of "9781782163145 LEARNING JQUERY FOURTH ...
Looking at the end result, it's clear that his skills as both a developer and a ... hiding content that we wanted people...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think this is fixed as of https://github.com/emberjs/ember-qunit/releases/tag/v5.1.3 (thanks @drewlee!)
We ran into this as well and use Development mode often and styles were off there. Adding this to the
<head>
in ourindex.html
file seems to have fixed most of the style issues