• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

coreui / coreui-pro / 43638971621
97%
main: 94%

Build:
Build:
LAST BUILD BRANCH: v6-dev
DEFAULT BRANCH: main
Ran 14 Nov 2026 08:45PM UTC
Jobs 1
Files 95
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

14 Nov 2026 08:43PM UTC coverage: 96.736% (-0.003%) from 96.739%
43638971621

push

github

web-flow
fix: read focus from the component's own root inside a shadow root (#1840)

Inside a shadow root `document.activeElement` is the host, so components
that compared it with their own elements got the wrong answer: Calendar
lost focus when a navigation button opened the months view and after
refresh(), Carousel dropped focus on a control it disabled, ChipSet
typeahead started from the first chip, the picker cleaner did not move
focus to the field, Tooltip with `anchors` described the anchor instead
of the focused control inside it, Transfer lost focus after a move,
Popup returned focus to the first element of the anchor instead of the
one that opened it and did not scroll the focused entry into view on
mobile, and announce() did not hold a message while focus sat in a
closing dialog inside a shadow root or on an element slotted into one.

The component sites now ask the document or shadow root their element
sits in, through a new `rootActiveElement()` in util/focus. NumberInput
reads its own root the same way, with no visible difference. The same
expression was written out by hand in ten places (Calendar, LoadingButton,
MultiSelect, OtpInput, Stepper, focus, focustrap, form-validation,
list-navigation); they use the util now. The hiding-dialog check in
announce() starts from the deepest focused element and walks up through
slots and shadow hosts, with the walk the modal lookup already used.

Left as they are: the fallen-to-body check at the end of Calendar's
`_keepingFocus` and the one in chip.ts ask whether focus fell to the body
of the whole document, which `document.activeElement` answers correctly
in a shadow root too; context-menu.ts keeps its read because it needs the
root itself for deepActiveElement().

Each fix has a shadow-root spec that fails with it reverted, apart from
Carousel's blur fallback, which Chromium and Firefox make redundant by
dropping focus from a disabled control themselves. One more announce spec
guards against reading the dee... (continued)

8428 of 8931 branches covered (94.37%)

Branch coverage included in aggregate %.

33 of 33 new or added lines in 17 files covered. (100.0%)

14158 of 14417 relevant lines covered (98.2%)

2331.97 hits per line

Jobs
ID Job ID Ran Files Coverage
1 43638971621.1 14 Nov 2026 08:45PM UTC 95
96.74
GitHub Action Run
Source Files on build 43638971621
  • Tree
  • List 95
  • Changed 17
  • Source Changed 17
  • Coverage Changed 14
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #43638971621
  • db1114ad on github
  • Prev Build on v6-dev (#43524621011)
  • Next Build on v6-dev (#43643855351)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc