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

coreui / coreui-pro / 30944146876
93%
main: 94%

Build:
Build:
LAST BUILD BRANCH: v6-dev
DEFAULT BRANCH: main
Ran 04 Aug 2026 07:39PM UTC
Jobs 1
Files 61
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

04 Aug 2026 07:37PM UTC coverage: 92.965% (+0.02%) from 92.949%
30944146876

push

github

web-flow
feat(PasswordInput)!: build the frame and the toggle, like Number Input (#695)

* feat(PasswordInput)!: build the frame and the toggle, like Number Input

The component already owned the icon; it owns the button and the frame that
lays it out now, so the markup is a plain form control:

  <input type="password" class="form-control" data-coreui-toggle="password-input">

data-coreui-toggle moves from the button to the input - there is no button
in the markup to put it on - and its value becomes the component's name, so
it reads the same as Number Input's.

The wrapping is one helper shared by both components rather than a copy in
each: ensureControlGroup / releaseControlGroup in util/form-control-group.
It carries the rule Number Input arrived at, that every class except
.form-control moves to the frame, because a class on the control describes
the field and the field is the frame once it is wrapped.

The accessible name of the toggle is an option now (ariaToggleLabel), since
the button is no longer the author's to label.

* test(visual): commit the Linux baselines so CI actually compares

The Visual job has been passing on every pull request by generating
baselines rather than checking against them: with no *-chromium-linux.png
in the tree, the matcher creates the set and the run ends green. Visual
regressions were only ever caught on a maintainer's machine.

These are the 33 the job generated on this branch, so they carry the
markup this pull request settles. The next run compares.

* docs(NumberInput): correct an overstated verification claim

The comment said the spinner rules were verified in all three engines.
Two were measured; Playwright's WebKit would not launch here, which the
pull request body said and the comment did not. It now states what was
measured and what each rule leaves behind when used alone.

* docs(NumberInput): record that Safari was checked by hand

4268 of 4821 branches covered (88.53%)

Branch coverage included in aggregate %.

49 of 0 new or added lines in 0 files covered. (NaN%)

2 existing lines in 2 files now uncovered.

8272 of 8668 relevant lines covered (95.43%)

362.5 hits per line

Coverage Regressions

Lines Coverage ∆ File
1
64.63
-0.61% js/src/navigation.ts
1
91.07
5.62% js/src/password-input.ts
Jobs
ID Job ID Ran Files Coverage
1 30944146876.1 04 Aug 2026 07:39PM UTC 61
92.96
GitHub Action Run
Source Files on build 30944146876
  • Tree
  • List 61
  • Changed 4
  • Source Changed 3
  • Coverage Changed 4
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #30944146876
  • e8795e23 on github
  • Prev Build on v6-dev (#30938685324)
  • Next Build on v6-dev (#30958941902)
  • 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