w3c / w3c/afrlreq

Text opacity shows glyph overlap

Open
#14 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

doc:adlm doc:nkoo gap i:cursive l:ff l:nqo p:advanced s:adlm s:nkoo x:adlm x:alreq x:blink x:gecko x:nkoo
Dominant language
HTML
Stars
11
Forks
4
PR merge metrics
No merged PRs in 30d

Description

This issue is likely to apply to all cursive script text.

Text in 'cursive' writing systems is joined by overlapping glyphs with the appropriate joining forms. If those glyphs are made opaque, the joins should not become apparent. For example, N'Ko should look like this:

Screenshot 2022-02-01 at 15 02 18

The GAP

When opacity is applied to text, some browsers produce dark patches where the cursive glyphs overlap. Here is an example in the Adlam script.

Screenshot 2021-01-22 at 15 52 10

And here is an N'Ko example.

Screenshot 2021-02-16 at 09 01 14

Gecko and Blink browsers show the unwanted overlaps. WebKit works as expected for Arabic, Devanagari, Syriac & N'Ko, but not for Adlam (Fulah), Mongolian, or Hanifi Rohingya.

Tests

Interactive test, Applying opacity to cursive text doesn't produce dark patches where glyphs overlap

I18n test suite, Text opacity

Contains similar tests for Arabic and Mongolian text, with the same results, except that WebKit browsers don't display Mongolian as cursive text, so the test is moot in that case.

Action taken:

Issue, Add note for text opacity applied to cursive scripts Closed.

Browser bug reports:

GeckoBlinkWebKit

Outcomes:

2020-07-27: css-color was updated to clarify that opacity should be applied to a whole element, not to individual letters, so that this shouldn't happen.

Priority:

Marking as advanced, since this is a decorative feature.

Contributor guide

Open the contributing guide

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

Start with the linked interactive test, the i18n test suite's cursive text opacity results, and the CSS Color 4 transparency clarification. Compare the documented Gecko, Blink, and WebKit reports; the issue's stated outcome is that opacity applies to the whole element without visible glyph-overlap patches.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
internationalization, web-dev
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.