Avoid potentially adding invalid attributes or duplicates for dominant color images#578
Conversation
felixarntz
left a comment
There was a problem hiding this comment.
@pbearne While the approach for the fix makes sense to me, there are still a few flaws in the concrete logic.
One larger problem is that the logic now doesn't check whether the $style variable is not empty individually, which means that the else clause now can add a style="" - we don't want that.
See related comments below.
Co-authored-by: Felix Arntz <[email protected]>
Co-authored-by: Felix Arntz <[email protected]>
felixarntz
left a comment
There was a problem hiding this comment.
@pbearne There is some overlap between this PR and #582.
Both of the PRs have something useful in them, but one part of #582 is a cleaner solution than the one here, while the PR here covers a few more problems. Therefore I added a suggestion below to limit your PR here to avoiding the addition of invalid attributes or duplicates from calling this function multiple times on the same image.
felixarntz
left a comment
There was a problem hiding this comment.
@pbearne One more point of feedback here.
|
Will take over this one since it's a bug so we should get it merged today for the 1.7.0 plugin release. |
|
@costdev I've made the relevant updates here, this should be ready for another review. Would be awesome if you could get to it today so we can merge it to get the release branch ready. |
…nd-inline-styling
|
Changed the base branch here to |
Summary
Fixes #577
Relevant technical choices
Checklist
[Focus]orInfrastructurelabel.[Type]label.no milestonelabel.