I wonder if the invokers proposal could take the place of the scroll buttons proposal?

[mfreed7]

Please see the Invokers Proposal for details. But that API proposal allows any button to "target" any other element, and provide an action to take on that target. It seems like scroll up/down might make a good use case for this API? As in

<div id=scroller> Content </div>
<button id=scroll_up invoketarget=scroller invokeaction="scroll up"> UP </button>

@keithamus

[flackr]

Thanks for the suggestion. That could certainly work. I'd say the dedicated pseudo element has two main advantages over this:

• the HTML can be just the content, e.g. the carousel HTML in the demo is effectively a plain list of items.
• The linkage to the scroller is automatic, so the same pattern can be shared by multiple scrollers without needing unique scroller ids. E.g. it is common for a single vertically scrolling page to have multiple horizontal caroursels.

That said, invokers could still work well if we decide not to pursue dedicated pseudo elements, or even be the underlying explanation for how these buttons work.

[mfreed7]

Hmm, both of your advantages are indeed compelling. I'm inclined to agree! Feel free to close this and just keep Invokers in mind, should the current proposal fall apart. Thanks!

[flackr]

I suspect as with the scroll marker issue that there will be value in having this as an explanation for what the generated pseudo-elements do internally and how you could turn arbitrary elements into scroll buttons.