lukejacksonn / lukejacksonn/oceanwind

"sticky" utility class seems to end up with an empty translation

Open
#43 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
264
Forks
11
PR merge metrics
No merged PRs in 30d

Description

Interesting bug I came across is that the .sticky utility class ends up with an empty translation in the browser. There's no warning about the lack of a translation either. By all means it looks to be set up correctly, no typo in the translation or anything and all other position short-hands work.

It's late here, so I'll have to explore & get a reproduction tomorrow. I just wanted to get this down before I forgot.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named. Start by reproducing the .sticky utility in a browser and compare its generated translation with the other position shorthand utilities. Done means identifying why .sticky produces an empty translation and adding coverage for the behavior, including the missing-translation warning if appropriate.

Written by the indexing model from the issue text.

Assessment

Tech stack
css, javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.