Instead of keeping a member of SVGPropertyAccess in each SVGProperty, we can walk through the SVGPropertyOwner chain till we reach an owner of type SVGAnimatedProperty or SVGAnimatedPropertyList. This owner compares the property to be modified with its animVal. And if they are the same, it will return 'true' through its virtual method isPropertyReadOnly().
Created attachment 379919 [details] Patch
Created attachment 379921 [details] Patch for review
Comment on attachment 379921 [details] Patch for review Nice, and much cleaner.
You missed at least one instance where SVGPropertyAccess was still used: SVGFitToViewBox.
(In reply to Nikolas Zimmermann from comment #4) > You missed at least one instance where SVGPropertyAccess was still used: > SVGFitToViewBox. It is removed in https://bugs.webkit.org/show_bug.cgi?id=202411 which blocks this bug. The accumulated patch above includes this change. The "Patch for review" is the difference between the accumulated patch and the batch of the other bug. I post patches this way to be not blocked by the code review.
(In reply to Said Abou-Hallawa from comment #5) > (In reply to Nikolas Zimmermann from comment #4) > > You missed at least one instance where SVGPropertyAccess was still used: > > SVGFitToViewBox. > > It is removed in https://bugs.webkit.org/show_bug.cgi?id=202411 which blocks > this bug. The accumulated patch above includes this change. The "Patch for > review" is the difference between the accumulated patch and the batch of the > other bug. I post patches this way to be not blocked by the code review. Sorry, I missed that :-( I wish we had a git based workflow, where we could upload a branch containing two commits that can be reviewed independently, but landed together :-)