-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
updated to v2 almost complete #1
Comments
Maybe open a v2 branch for this? |
Yes please
…On Oct 18, 2017 8:32 PM, "KIP" ***@***.***> wrote:
Maybe open a v2 branch for this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAICys0JLxb0-78Tjxe0hkc0LuSgTQeXks5stsLmgaJpZM4P-p4A>
.
|
Okay I just forked it. I'll probably make a pull request tonight. Just got to move the x-toggle over to the x-tabbox. -edit --always do this...found one that does the same thing You interested in creating a x-toggle component repo here? |
alright I just got the demo up and running I'm going to make a pull request soon....After some COD....:) |
https://kipomaha.github.io/kipsTabbox/demo/index.html |
I got a new PR that could go with alpha. It was part of a diff lib that I was building on my own. It was based off of what I saw in v2 from before => no custom elements or prototyping...but implemented a type=>mode hierarchy. You could add diff types and assign modes to those types. Info was passed to the object by using a build() function that read the functions return value. In any case I made a cordial little Regards Steve |
|
Not that you wanted to look at that in this form, but could you let me know if you want this as a PR. So you can take a better look. |
Also are you still using the same component stub? |
It hasn't been updated from v1, but probably needs to be.
…On Wed, May 23, 2018, 6:01 PM KIP ***@***.***> wrote:
Also are you still using the same component stub?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAICyhCAv8_bco3fwk77Sdxp_rvtp2hzks5t1gZYgaJpZM4P-p4A>
.
|
Its all the same except for the selectEvent gets wrapped around an event function. |
what do you think of using the extensions like that or should I just pass the definition straight through VIA create. I was going to do it the direct way, but decided that people could use the create method I was think that this would be a good way to get contributors to extend V1 components a little bit more creatively. What do you think? |
Than again I think that XTagElement is all you need for that too lol.. there are so many ways to do things with this one @csuwildcat |
The keyboard shortcuts don't go backwards only forwards. I don't know if this is intended behavior I think it is. Would you accept a pull request where you press left or right and enter so the direction can be controlled instead of tab + enter? I am updating x-tabbox to react that way in V2 so it deviates from the specs from v1. EDIT: meant tab and left or right arrow, but I think that it would be better to not override normal browser behavior and use |
@csuwildcat do you want a pull request for a v2 version?
The text was updated successfully, but these errors were encountered: