Codeinwp / Codeinwp/otter-blocks
Otter Section Block: Default Text Color doesn't work Correct
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 198
- Forks
- 36
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 30
Description
Description
When the Otter Block section is used with the default WP Gutenberg Blocks, the default color of the text doesn't get implemented correctly according to the background color but if the Otter Section Block is not used, the text color behaves correctly.
Step-by-step reproduction instructions
- Go to the page and add Otter Section Block with one column.
- Give that Section the background color Black.
- Add default Gutenberg Columns Block in the Section and select two columns.
- In the left column, add a background color white.
- Add a default paragraph block.
- The color of the paragraph should be black but it will be white.
Although the color can be simply changed and there will be no issue after that, but the customer says he doesn't want to do that and it should work by default.
Screenshots, screen recording, code snippet or Help Scout ticket
Help Scout: https://secure.helpscout.net/conversation/2341506966/383163?folderId=212385
Screen Recording of the issue: https://share.getcloudapp.com/04uvlnQd
Environment info
No response
Is the issue you are reporting a regression
No
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
Reproduce the issue with an Otter Section Block, a black section background, a white nested Gutenberg column, and a paragraph block. Inspect the Otter Section styling and compare it with the paragraph’s default color behavior outside the section; done means the paragraph is black by default in the white column without manual color changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100