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

wrench frame saving producing incorrect results #1402

Closed
Gankra opened this issue Jun 19, 2017 · 0 comments
Closed

wrench frame saving producing incorrect results #1402

Gankra opened this issue Jun 19, 2017 · 0 comments

Comments

@Gankra
Copy link
Contributor

@Gankra Gankra commented Jun 19, 2017

If I open this in servo with -Zwr-record

<html>
<body style="background-color: rgb(255,0,0)">
<iframe style="position: fixed; top: 10.5" src="data:text/html,<body style='background-color: rgba(0,0,255,0.5)'>">
</iframe>
</body>
</html>

And then replay it in wrench, it renders correctly. However if I tell it to save the results to json/yaml, the results are incorrect and attempting to show them produces something different.

There's two problems:

  1. the outer document and inner document show up as seperate frames (weird/confusing, but usable)

  2. several bounds get changed. For instance the inner document produces this:

---
root: 
  items: 
    - 
      bounds: [0, 0, 300, 150]
      clip: [0, 0, 0, 0]
      "clip-and-scroll": 0
      type: "stacking-context"
      "scroll-policy": scrollable
      "transform-style": flat
      items: 
        - 
          bounds: [8, 8, 284, 0]
          clip: [-8947849, -8947849, 17895698, 17895698]
          "clip-and-scroll": 0
          type: rect
          color: 0 0 255 0.5020
  id: [0, 0]
pipelines: []

Note that the bounds describe a 284x0 rectangle, where it should actually be 300x150. The 8x8 offset should also presumably be 0x0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.