Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Take origin from current window instead of creating a new one in event of reflow #25777

Merged
merged 2 commits into from Feb 19, 2020

Commits on Feb 15, 2020

  1. Take origin from window instead of creating a new one in case of reflow

    Everytime a new LayoutContext was created, it created a new origin which
    caused endless stream of image loads to occur in case of reflow. The reason
    for this was that the existing image, although cached successfully, was not
    used because the entry in hashmap did not match because of different(new)
    origin.
    This is solved by storing the origin of a window in enum ScriptReflow and
    used in creating new LayoutContext in case of reflow.
    kunalmohan committed Feb 15, 2020

Commits on Feb 17, 2020

You can’t perform that action at this time.