GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — aria-valuenow set incorrectly when only the second pane is sized · Issue #362 · angular-split/angular-split

aria-valuenow set incorrectly when only the second pane is sized #362

New issue
Copy link
New issue
Copy link
Closed
#368
Closed
aria-valuenow set incorrectly when only the second pane is sized#362
#368
Copy link
Labels
bug

Description

@kainiedziela
kainiedziela
opened on Oct 30, 2023
Issue body actions

When size is set for the second of two panes only the gutter element has set aria-valuenow to *, which is not a valid value for this attribute and results in accessibility issues.

To reproduce, create this minimal boilerplate:

<as-split>
  <as-split-area></as-split-area>
  <as-split-area size="30"></as-split-area>
</as-split>

and check the .as-split-gutter element, now with aria-valuenow incorrectly set to *

Activity

  1. kainiedziela
    added
    bug
    on Oct 30, 2023
  2. Harpush commented on Nov 26, 2023

    @Harpush
    Harpush
    on Nov 26, 2023
    Collaborator
    More actions

    Is it a regression? We recently did some work around wildcard areas.
    What is the expected valuenow then? Nothing (null) or th real amount calculated with respect to being a wildcard area?

  3. kainiedziela commented on Nov 28, 2023

    @kainiedziela
    kainiedziela
    on Nov 28, 2023
    Author
    More actions

    I believe it is a regression, at least it has not come up in our tests before.

    I'd say ideally it would be the real amount (0.7 in that example), but no attribute at all would be better than the invalid one used currently.

  4. beeman
    closed this as completedin #368on Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bug

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.