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

Document why calls to methods like force_relayout are required #5329

Open
jdm opened this issue Mar 23, 2015 · 2 comments · May be fixed by #23118
Open

Document why calls to methods like force_relayout are required #5329

jdm opened this issue Mar 23, 2015 · 2 comments · May be fixed by #23118
Assignees

Comments

@jdm
Copy link
Member

@jdm jdm commented Mar 23, 2015

For htmltextareaelement.rs and htmlinputelement.rs, it's not always clear at first glance why we need to explicitly mark the node as dirty and force a reflow to take place. We should document these reasons.

@tetsuharuohzeki
Copy link
Member

@tetsuharuohzeki tetsuharuohzeki commented Mar 24, 2015

@jdm Josh, is this a your reminder? (implicitly assigned to you?)

@jdm
Copy link
Member Author

@jdm jdm commented Mar 24, 2015

Yes, unless anybody else wants to.

@jdm jdm self-assigned this Mar 24, 2015
@jdm jdm linked a pull request that will close this issue Mar 27, 2019
4 of 4 tasks complete
bors-servo added a commit that referenced this issue Mar 28, 2019
Remove unnecessary explicit reflows

These should be unnecessary since the introduction of the catch-all reflow in #9421. Any explicit reflow that is not performing a layout query is unnecessary, and we should be postponing reflow for as long as possible. This should allow pages to perform better when processing mouse events, for example, and allow profiles to better reflect the actual work being done by a page.

---
- [x] `./mach build -d` does not report any errors
- [x] `./mach test-tidy` does not report any errors
- [x] These changes fix #5329
- [x] There are tests for these changes

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/23118)
<!-- Reviewable:end -->
bors-servo added a commit that referenced this issue Apr 9, 2019
Remove unnecessary explicit reflows

These should be unnecessary since the introduction of the catch-all reflow in #9421. Any explicit reflow that is not performing a layout query is unnecessary, and we should be postponing reflow for as long as possible. This should allow pages to perform better when processing mouse events, for example, and allow profiles to better reflect the actual work being done by a page.

---
- [x] `./mach build -d` does not report any errors
- [x] `./mach test-tidy` does not report any errors
- [x] These changes fix #5329
- [x] There are tests for these changes

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/23118)
<!-- Reviewable:end -->
bors-servo added a commit that referenced this issue Apr 9, 2019
Remove unnecessary explicit reflows

These should be unnecessary since the introduction of the catch-all reflow in #9421. Any explicit reflow that is not performing a layout query is unnecessary, and we should be postponing reflow for as long as possible. This should allow pages to perform better when processing mouse events, for example, and allow profiles to better reflect the actual work being done by a page.

---
- [x] `./mach build -d` does not report any errors
- [x] `./mach test-tidy` does not report any errors
- [x] These changes fix #5329
- [x] There are tests for these changes

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/23118)
<!-- Reviewable:end -->
bors-servo added a commit that referenced this issue Apr 9, 2019
Remove unnecessary explicit reflows

These should be unnecessary since the introduction of the catch-all reflow in #9421. Any explicit reflow that is not performing a layout query is unnecessary, and we should be postponing reflow for as long as possible. This should allow pages to perform better when processing mouse events, for example, and allow profiles to better reflect the actual work being done by a page.

---
- [x] `./mach build -d` does not report any errors
- [x] `./mach test-tidy` does not report any errors
- [x] These changes fix #5329
- [x] There are tests for these changes

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="34" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/23118)
<!-- Reviewable:end -->
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.

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