Closed
Bug 1758753
Opened 4 years ago
Closed 4 years ago
Migrate XPCOM hashtable documentation from MDN archive to Firefox Source Docs
Categories
(Core :: XPCOM, task)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
100 Branch
| Tracking | Status | |
|---|---|---|
| firefox100 | --- | fixed |
People
(Reporter: mconley, Assigned: mconley)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
48 bytes,
text/x-phabricator-request
|
Details |
The using_cxx_in_firefox_code.rst documentation links to the now broken MDN documentation for XPCOM hashtables in multiple places.
I retrieved the hashtable documents from the MDN archive, used pandoc to convert them to rst, and tried to scrub out outdated information that I was aware of. Hopefully someone who uses our hashtables more often and knows about how they work deeply under the hood can take a look and make sure I didn't miss anything.
Original documents:
| Assignee | ||
Comment 1•4 years ago
|
||
Pushed by mconley@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/452423a65ba6
Migrate XPCOM hashtable documentation from MDN to Firefox Source Docs. r=nika
Comment 3•4 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox100:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
Updated•4 years ago
|
Component: Documentation Infrastructure → XPCOM
Product: Firefox Build System → Core
Comment 4•4 years ago
|
||
It looks like you accidentally introduced a change to Document.cpp when you landed this.
--- a/dom/base/Document.cpp
+++ b/dom/base/Document.cpp
@@ -14585,17 +14585,17 @@ void Document::GetWireframeWithoutFlushi
}
auto& wireframe = aWireframe.SetValue();
wireframe.mCanvasBackground = shell->GetCanvasBackground();
FrameForPointOptions options;
options.mBits += FrameForPointOption::IgnoreCrossDoc;
options.mBits += FrameForPointOption::IgnorePaintSuppression;
- options.mBits += FrameForPointOption::OnlyVisible;
+ // options.mBits += FrameForPointOption::OnlyVisible;
AutoTArray<nsIFrame*, 32> frames;
const RelativeTo relativeTo{rootFrame, mozilla::ViewportType::Layout};
nsLayoutUtils::GetFramesForArea(relativeTo, pc->GetVisibleArea(), frames,
options);
// TODO(emilio): We could rewrite hit testing to return nsDisplayItem*s or
// something perhaps, but seems hard / like it'd involve at least some extra
Flags: needinfo?(mconley)
Pushed by apavel@mozilla.com:
https://hg.mozilla.org/mozilla-central/rev/432bf7d2d4ec
reverted commented line a=backout
You need to log in
before you can comment on or make changes to this bug.
Description
•