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
There is a bug where using 'page' as the identifier to mean the entire webpage will trigger below error message. The tests for Yahoo website and DuckDuckGo did not pick this up because there are elements on both webpages that match the page identifier string.
[TAGUI][ERROR] - cannot find page
Raising this issue to commit a bugfix for the affected functions snap() and read().
The text was updated successfully, but these errors were encountered:
kensoh
changed the title
snap() and read() - using page to mean entire webpage does not work
snap() and read() - using page to mean webpage does not work
Sep 2, 2019
#36 - add link to license in tagui.py to facilitate air-gap deployments (without internet access to pip)
# 50 - add frame() function to access web page frames (supports main frame and sub frame). add popup() function to access webpage popup tabs launched from webpage.
#52 - bugfix for snap() and read(), when 'page' is used to mean entire webpage a 'cannot find page' error message appears.
Bugfix implemented in v1.11 and available with pip install tagui --upgrade.
Now snapping screenshots of the webpage, and reading HTML text of the webpage work.
kensoh
changed the title
snap() and read() - using page to mean webpage does not work
snap() and read() - using page to mean webpage does not work [fixed]
Sep 2, 2019
oops, missed out 1 line when pushing previous commit. somehow that line in snap() wasn't selected to push.
---
#36 - add link to license in tagui.py to facilitate air-gap deployments (without internet access to pip)
#50 - add frame() function to access web page frames (supports main frame and sub frame). add popup() function to access webpage popup tabs launched from webpage.
#52 - bugfix for snap() and read(), when 'page' is used to mean entire webpage a 'cannot find page' error message appears.
There is a bug where using 'page' as the identifier to mean the entire webpage will trigger below error message. The tests for Yahoo website and DuckDuckGo did not pick this up because there are elements on both webpages that match the page identifier string.
Raising this issue to commit a bugfix for the affected functions snap() and read().
The text was updated successfully, but these errors were encountered: