Conversation
ameerabuf
left a comment
There was a problem hiding this comment.
I agree with the direction, and it does seem to be the same information in much less text, but I do not feel comfortable removing so much without first testing to see there is no regression. We can use Monty's QA-flow on this branch or something like this...
Added customEffect rules to hover and click; Fixes to viewprogress.md
Added missing composite effect property in types
Added TOCs
ameerabuf
left a comment
There was a problem hiding this comment.
read click and hover. There were already quite a few comments, some are critical IMO, so I submit now and I will continue with the other triggers.
| // Use keyframeEffect, namedEffect, or customEffect as in Rules 1–2 | ||
| keyframeEffect: { name: '[EFFECT_NAME]', keyframes: [EFFECT_KEYFRAMES] }, |
There was a problem hiding this comment.
then let's not write a template of a keyframeEffect, it is just confusing
There was a problem hiding this comment.
Do you have another suggestion?
ameerabuf
left a comment
There was a problem hiding this comment.
Approved to allow merge and to proceed working on it. However, there are many unresolved comments that were not handled and I think are important, some even critical. I keep them unresolved so we can return to them in the future.
Description
hover.mdclick.mdviewprogress.mdviewenter.mdpointermove.mdintegration.mdscroll-list.mdfull-lean.md