diff options
author | FranklinDM <mrmineshafter17@gmail.com> | 2022-04-18 23:17:24 +0800 |
---|---|---|
committer | FranklinDM <mrmineshafter17@gmail.com> | 2022-04-18 23:21:58 +0800 |
commit | 37c86f2c0746a31cfe96309bf3e390e7573b3b3a (patch) | |
tree | 937dcd3baa5a8317610dd4a81200b36e8a7a9e10 /tools | |
parent | 8d8da66f9400e8929e7bd6051d785bbdd02c6340 (diff) | |
download | uxp-37c86f2c0746a31cfe96309bf3e390e7573b3b3a.tar.gz |
Issue #1873 - Part 2: Ensure normalized parent is used for UndisplayedMap handling code
We have four entry points that deal with the parents of display:none/ display:contents content. These are the functions for setting, changing, getting and removing a style context. Or more specifically:
GetStyleContextInMap called by GetDisplay[None|Contents]StyleFor
SetStyleContextInMap called by RegisterDisplay[None|Contents]StyleFor
ChangeStyleContextInMap called by ChangeRegisteredDisplay[None|Contents]StyleFor
UnregisterDisplay[None|Contents]StyleFor okay, this is actually two functions, but they act as a pair
This change makes all these functions call GetApplicableParent up front and act on and pass around the parent that it returns. This is so that throughout the code we are always handling the parent that will be used as the key in the UndisplayedMap entry. This is necessary so that all the code that sets/gets the 'MayHaveChildrenWithLayoutBoxesDisabled' bit on/from an nsIContent object is using the same object, otherwise everything breaks down.
Partially based on part 2 of https://bugzilla.mozilla.org/show_bug.cgi?id=1367214
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions