Context Navigation

Changes between Initial Version and Version 1 of Ticket #28712, comment 5

initial	v1
2	2	> As for the case of styling, wouldn't it involve less markup to set a class on the `<select>` and use a CSS selector (e.g. `select.super option {...}`) for that? If anything, I'd think we'd want a way to specify a different attribute value for each `<option>` value -- setting the same key/value on every `<option>` doesn't seem like something to encourage.
3	3
4		You're right that the implementation in the PR was not very powerful. I have now expanded the PR to allow for callable attribute values. This would allow developers a lot of control over the attributes of each option.
	4	You're right that the implementation in the PR was not very powerful. I have now expanded the PR to allow for callable attribute values. When a callable is passed as an attribute value it is separately evaluated for each option and the returned value is used. This would allow developers a lot of control over the attributes of each option.