Forum Discussion

Mike359's avatar
Mike359
Contributor
4 days ago

page.PagePicture - Screenshot duplication

Hi everyone, I seem to have an intermittent issue when using the method page.PagePicture(0,0,-1,-1) with Oracle Cloud Applications. If I try to capture a screenshot of a full page (e.g., var shot...
Mike359's avatar
Mike359
Contributor
3 days ago

Hi, Thank you for replying. I have tried the solution many times and as I stated this is an  intermittent error no matter what settings I apply. Here are some redacted screen shots of what happens when I run the test several times without changing any code:

Expected Output:

Occasionally I will get this Unexpected output (with no changes in code):

As you can see it is repeated [Note: I manually redacted data on the screenshot in obvious places for Data Protection reasons]

rraghvani's avatar
rraghvani
Icon for Champion Level 3 rankChampion Level 3
3 days ago

What you have shown is what is explained in the Remarks section in the link that I had provided, relating to "sticky" elements.

Try using Options.Web.CSSTransitionForPagePicture property to see if that helps.

  • Mike359's avatar
    Mike359
    Contributor
    3 days ago

    Thanks, but that was the first thing I did. :( 

    • Options.Web.CSSTransitionForPagePicture (tested with both true and false)

     

    (as per above) - BTW the heading in OracleCloud Applications is not sticky.

      • Mike359's avatar
        Mike359
        Contributor
        3 days ago

        Thank you for your response. To be honest, I have been dealing with this issue for quite some time and have tried various solutions suggested by AI tools. After each TestComplete upgrade, I revisit these solutions and test them again by uncommenting the relevant code in my scripts.

        I thought it would be best to reach out to the community (experienced users like yourself) to confirm whether I might have missed any workarounds that others may have discovered. I want to ensure I’ve explored all possible options before logging this as a bug, as I anticipate it could be a challenging and time-consuming process to identify and resolve.