nextcloud / nextcloud/calendar

Semantic HTML errors

Open
#4,281 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Steps to reproduce

This is an accessibility issue.

There are some validation errors regarding code semantics that doesn’t follow the standard.

Make sure, that

  1. Elements have complete start and end tags.
  2. Elements are nested according to their specifications.
  3. Elements do not contain duplicate attributes.
  4. Any IDs are unique.
  5. li-elements are inside of ul/ol-elements.
Expected behavior

Semantic is right.

Actual behaviour

Sometimes semantic is wrong.

  • Elements with identical id-values
  • svg-elements with alt-attributes
  • li-elements outside of ul/ol-elements
Calendar app version

3.3.2

CalDAV-clients used

No response

Browser

No response

Client operating system

No response

Server operating system

No response

Web server

No response

Database engine version

No response

PHP engine version

No response

Nextcloud version

No response

Updated from an older installed version or fresh install

No response

List of activated apps

No response

Nextcloud configuration

No response

Web server error log

No response

Log file

No response

Browser log

No response

Additional info

No response

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

No files, tests, or entry points are named. Start by reproducing the reported validation errors in the calendar UI and locate the markup producing duplicate IDs, SVG alt attributes, and out-of-list li elements; done means the listed semantic checks pass without those errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
html, javascript
Domain
accessibility, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.