Context Navigation

Changes between Initial Version and Version 1 of Ticket #48368, comment 15

initial	v1
5	5	I'm going to give the same answer :) Some ''visual'' changes came from the design team and they are design improvements implemented on top of the accessibility improvements. Worth noting Gutenberg already uses this specific style for `<select>` elements since several months. Consistency in the design across the admin is important and I guess we all agree to not have 2 different select styles in WordPress.
6	6
7		From an accessibility perspective, it really doesn't matter if a select uses native arrows or a custom arrow, as long as the control can be clearly identified as a select. Questions on similar visual changes should be asked to the design team. For what is wo~~art,~~ I personally support these changes.
	7	From an accessibility perspective, it really doesn't matter if a select uses native arrows or a custom arrow, as long as the control can be clearly identified as a select. Questions on similar visual changes should be asked to the design team. For what is worth I personally support these changes.
8	8
9	9	Regarding the WPSSO plugin, from what I see it uses custom CSS for the form controls. I do understand that many plugins have been forced for years to customize the styling of the core form controls because... let's face it: the core styles weren't great. Several inconsistencies in the default heights, paddings, etc., made alignments look far from ideal.