Comments (3)
The failure is reproducible on linux with CfT. According to the logs, the root cause is the CfT info bar. For whatever reason, (with some other preconditions) right after navigation the viewport dimensions don't not include infobar, however visually it is there. After 0.5 seconds the viewport is changed to respect the info bar. The test does the following:
- Get the viewport dimensions.
- Navigate to a page with an element below the viewport.
- Try to get the element's screenshot.
- Expect
webdriver.bidi.error.UnableToCaptureScreenException
to be raised, as the element is out of the viewport.
The test is failing, as after the navigation (with some unknown preconditions, reproducible by running document
test) the viewport does not include infobar anymore, and the element is actually in the viewport, so the screenshot can be taken.
from chromium-bidi.
We should disable Chrome info bars in WPT to reduce the test flakiness.
UPD: done in web-platform-tests/wpt#45801
from chromium-bidi.
from chromium-bidi.
Related Issues (20)
- The capability to ignore cert errors should be browser-wide HOT 2
- Adopt the webdriver-bidi-protocol package
- OOPIFs are not recovered on reconnect HOT 3
- Emit `browsingContext.fragmentNavigated` event when traversing history
- Implement network.setCacheBehavior HOT 2
- Huge `id` of command does turn into a floating number in answer HOT 3
- Implement Chrome-specific PDF and Screenshot options
- Network Request bodySize may not always be computed correctly
- Pending release fails one Puppeteer test HOT 3
- [Feature] Mechanism to retrieve supported Chrome stable version
- Bug: network requests that happen before the page load a sometimes emitted after it HOT 1
- Bug: chromium-bidi auto-attaches to custom CDP sessions created over bidi+
- Feature: subscribing to specific CDP events does not work for user-facing CDP sessions HOT 1
- The fragmentNavigated is emitted on the history updates that are not fragment navigations HOT 1
- Support Chrome cookie partition keys HOT 1
- run-e2e.mjs and run-bidi-server.mjs should kill child process on exit HOT 1
- Interop tests override logs HOT 2
- WPT test failures are not reported
- Update the workflows that publish changes HOT 1
- Feature: show version in BiDi-CDP Mapper tab HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from chromium-bidi.