| Summary: | Remove extra call to 'layout' in Document::setParsing | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ahmad Saleem <ahmad.saleem792> |
| Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW --- | ||
| Severity: | Normal | CC: | ap, bfulgham, simon.fraser, webkit-bug-importer, zalan |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari Technology Preview | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
|
Description
Ahmad Saleem
2023-03-05 15:02:50 PST
It looks like at this point this merge would only including the renaming part (WebKit does not schedule layout inside Document::setParsing) (In reply to zalan from comment #1) > It looks like at this point this merge would only including the renaming > part (WebKit does not schedule layout inside Document::setParsing) fireLayoutRelatedMilestonesIfNeeded() <- function, does it cause 'relayout'? Just from reading the code, it seems to be "Milestone" related something. (In reply to Ahmad Saleem from comment #2) > (In reply to zalan from comment #1) > > It looks like at this point this merge would only including the renaming > > part (WebKit does not schedule layout inside Document::setParsing) > > fireLayoutRelatedMilestonesIfNeeded() <- function, does it cause 'relayout'? No, it is not supposed to. (In reply to zalan from comment #3) > (In reply to Ahmad Saleem from comment #2) > > (In reply to zalan from comment #1) > > > It looks like at this point this merge would only including the renaming > > > part (WebKit does not schedule layout inside Document::setParsing) > > > > fireLayoutRelatedMilestonesIfNeeded() <- function, does it cause 'relayout'? > No, it is not supposed to. Should I do PR for renaming purposes and get rid of FIXME, at least one less FIXME. As long as you are OK with 'm_isParsing' name instead of 'm_bParsing'? sounds good! |