You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 19, 2024. It is now read-only.
The initial layout of container should be different to one after adding class "vertical".
This means that if we don't add class "vertical" to the container the test should fail.
To my understanding the main idea of test - is to check that by applying property "--layout-vertical" it changes the layout to vertical and thus passing a test.
Actual outcome
Currently initial layout is the same as after we add class "vertical" to container.
You can simply check this by commenting or removing line 166 -> container.classList.add('vertical');
And the test still would pass.
Steps to reproduce
Open test page in a web browser.
Put a break-point at line 166.
Comment or remove line 166 -> container.classList.add('vertical');
Refresh page/test.
Test Result Status: passed.
Browsers Affected
Checked only at chrome.
Chrome
Firefox
Safari 9
Safari 8
Safari 7
Edge
IE 11
IE 10
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Wrong initial state of container.
Expected outcome
The initial layout of container should be different to one after adding class "vertical".
This means that if we don't add class "vertical" to the container the test should fail.
To my understanding the main idea of test - is to check that by applying property "--layout-vertical" it changes the layout to vertical and thus passing a test.
Actual outcome
Currently initial layout is the same as after we add class "vertical" to container.
You can simply check this by commenting or removing line 166 -> container.classList.add('vertical');
And the test still would pass.
Steps to reproduce
Browsers Affected
Checked only at chrome.
The text was updated successfully, but these errors were encountered: