There are three flags in that project. By pressing any of them, a custom function is run. Depending on which flag (or HTML element) is pressed, something similar (and yet unique) happens. The trick I use is to grab the ID of the element. Then, I use that ID to pull data from an array. It sounds complicated, but it's quite simple to do once you understand it.
I noticed people are buzzing about console.log(arguments) tonight, but maybe that free Hype template might help you out.
@Photics Oh cool! So you essentially created a local data store of properties tied to the element id so the function could be reused. Creative workaround! Will be definitely using this as inspiration if there is no direct way to pass an argument.
This please. Form elements especially for my general use would be especially helpful. I have to make accessible content, and thankfully due to the ability to directly edit the source of divs I can just code in buttons or other inputs, but it would be ideal to have actual button elements and not just divs behaving as buttons as proper keyboard input is required.
I would also like to see perhaps a panel or some other way to show the Inner HTML contents, as if you are loading a lot of content into an element on screen (doing some responsive design without using layouts, or loading tons of text into a div, for example), should that push the bottom of the element off screen, you can no longer easily reach the edit button. If you try to use the menu shortcut to edit the Inner HTML, the editor window is tied to the location of that edit button, so it remains off screen.
For my use case, I’m always editing the contents of elements on screen. Having the option to maybe open a UI panel that has the editor would be a welcome option, just to alway keep that showing the contents of elements selected since I’m usually jumping into the Inner HTML to edit.
