Fix issue #2 - SC.Buttons inside of form tags trigger form submission #3
Conversation
|
What about setting the button "type" attribute to "button", instead of the default of "submit"? Returning false from mouseUp does stop the form submission, but it seems like there's also a chance it would stop the event handling chain too early and prevent other event handlers from being called. Setting the "type" to "button" will make it not submit the form without affecting other event handling. |
|
Hey ebryn, What's the reason your button is inside a form tag, and is of type "submit" vs. "button"? |
|
It's being used inside an existing app, within an HTML form tag. SC isn't being used for data submission, the form tag is. I'm not explicitly setting the type of the button, I'm just using the standard SC.Button view. After doing a little research, it looks like the button tag defaults to a type of submit if it's not specified. Looking at the SC.Button source, it doesn't look like setting the type attribute is currently possible - perhaps it could be modified to support setting it? |
|
Closed since my original solution isn't the best approach. |
Use updated HTMLBars to vendor simple-html-tokenizer.
# This is the 1st commit message: typo in comment # The commit message #2 will be skipped: # indent yuidoc comment # The commit message #3 will be skipped: # remove IE8 test # The commit message #4 will be skipped: # remove commented out test # The commit message #5 will be skipped: # use file path and add imports # # Used RFC #176 modules API for imports. # Also cleaned up some of the globals-mode usage. # The commit message #6 will be skipped: # clean up more globals style documentation # The commit message #7 will be skipped: # Updates blueprints # The commit message #8 will be skipped: # remove extra type check # The commit message #9 will be skipped: # [BUGFIX beta] Reusing element causes problems in Safari # # When testing allowed input types, in some versions of Safari the type # cannot be change to `file` if previously set to a different one. # # Fixes #14727 # The commit message #10 will be skipped: # [DOC release]missed code block added # The commit message #1 will be skipped: # [DOC release] Update wait.js - Add missing backticks to code snippet. # The commit message #2 will be skipped: # use safe `toString` for array content in `mixins/array` # The commit message #3 will be skipped: # avoid expanding already expanded property key in computed.sort # The commit message #4 will be skipped: # avoid expanding already expanded property key in reduceMacro/arrayMacro/multiArrayMacro # The commit message #5 will be skipped: # [DOC release] Make `Ember.expandProperties` public # The commit message #6 will be skipped: # reuse meta `arrayContentDidChange` # The commit message #7 will be skipped: # replace `throw` with assertion in `enumerable` # The commit message #8 will be skipped: # [BUGFIX beta] Allow boolean values for current-when # # As the docs say, `A link will be active if current-when is true`. # Looks like this might have been broken since 1.13 and #12344 # did not seem to actually fix this particular bug. # # Related issues: # # - #12512 # - #12630 (fix was not merged) # - #12296 # The commit message #9 will be skipped: # remove unused imports # The commit message #10 will be skipped: # [DOC] Improve Ember.isEmpty # The commit message #1 will be skipped: # micro optimization in `enumerable`
Pretty simple fix.