Codeinwp / Codeinwp/otter-blocks
Automatic Transition Placement without any option to control
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 198
- Forks
- 36
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 30
Description
What problem does this address?
I, personally, find it very annoying and also few customers that when we are developing pages using Otter Blocks, it adds a transition of 0.3s to a lot of Elements like this: https://share.getcloudapp.com/xQuEbvXX and we don't have any default setting to turn it off from all the elements or from the specific elements.
This also creates a CLS issue when we load a page because the elements take 0.3s to settle to their position because of the transition property.
What is your proposed solution?
My proposed solution is to remove the transition property from being applied by default and place a transition setting in every Otter Blocks (where possible) so that Customer can set the transition as per his/her liking or preference.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating where Otter Blocks applies the default 0.3s transition to elements and review how block-specific settings are exposed. Confirm the desired behavior across the affected blocks, then verify that transitions are not applied by default and that supported blocks provide a usable transition control without causing the reported CLS issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100