Hi Team, While going through Blink's commit - I came across following, where we also have FIXME to rename function of similar: Blink Commit - https://chromium.googlesource.com/chromium/blink/+/56ef94099e79af642ee0ef5a3c8a3523c1ecc7dc WebKit Source - https://searchfox.org/wubkat/source/Source/WebCore/dom/Document.h#2319 etc. ^ There is FIXME as well in WebKit Source. Do we need to merge this or come-up with better name? Thanks!
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!
<rdar://problem/106621886>