Opened 2 years ago

Last modified 2 years ago

#6514 closed change

IOToggle Custom Element — at Version 2

Reported by: agiammarchi Assignee:
Priority: Unknown Milestone:
Module: User-Interface Keywords: UI, UX, component
Cc: greiner, saroyanm Blocked By:
Blocking: Platform: Unknown / Cross platform
Ready: no Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

Description (last modified by saroyanm)


We agreed on moving away from the current monolith approach to a more flexible, easier to debug, test, or update, components for our common needs.

Now that has been merged, it's time to start creating accessible Custom Elements for all new UI components we need (language list, tooltip, infinite filters, etc).

Being a fresh new approach, I suggest we start from most basic elements, trying to improve all of them for both development and for UX experience.

What to do

Convert existing Toggle element into a separate component.

Change History (2)

comment:1 Changed 2 years ago by agiammarchi

  • Cc greiner saroyanm added

comment:2 Changed 2 years ago by saroyanm

  • Description modified (diff)
  • Summary changed from [meta] Create Accessible UI Components to IOToggle Custom Element

Changed the description to reflect the change we are planing to land into the release.

Note: See TracTickets for help on using tickets.