Bug 1396025 - Write a comment to explain the difference between eBBoxIncludeFill/eBBoxIncludeStroke and eBBoxIncludeFillGeometry/eBBoxIncludeStrokeGeometry.
MozReview-Commit-ID: LD7uMh3D8vs
--- a/layout/svg/nsSVGUtils.h
+++ b/layout/svg/nsSVGUtils.h
@@ -384,18 +384,22 @@ public:
*/
static gfxMatrix AdjustMatrixForUnits(const gfxMatrix &aMatrix,
nsSVGEnum *aUnits,
nsIFrame *aFrame,
uint32_t aFlags);
enum BBoxFlags {
eBBoxIncludeFill = 1 << 0,
+ // Include the geometry of the fill even when the fill does not
+ // actually render (e.g. when fill="none" or fill-opacity="0")
eBBoxIncludeFillGeometry = 1 << 1,
eBBoxIncludeStroke = 1 << 2,
+ // Include the geometry of the stroke even when the stroke does not
+ // actually render (e.g. when stroke="none" or stroke-opacity="0")
eBBoxIncludeStrokeGeometry = 1 << 3,
eBBoxIncludeMarkers = 1 << 4,
eBBoxIncludeClipped = 1 << 5,
// Normally a getBBox call on outer-<svg> should only return the
// bounds of the elements children. This flag will cause the
// element's bounds to be returned instead.
eUseFrameBoundsForOuterSVG = 1 << 6,
// https://developer.mozilla.org/en-US/docs/Web/API/Element/getBoundingClientRect