Skip to content
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

Spark crash on select attribute typo #512

Closed
jpmx opened this issue Nov 28, 2012 · 4 comments
Closed

Spark crash on select attribute typo #512

jpmx opened this issue Nov 28, 2012 · 4 comments

Comments

@jpmx
Copy link

jpmx commented Nov 28, 2012

Ex. <select name="pick" class"typo">

Tested with
Meteor 0.5.2 & devel
Mac Chrome Version 23.0.1271.91

Reproduction recipe:

git clone git://github.com/jpea/spark-patch-bug.git

And watch console

@glasser
Copy link
Contributor

glasser commented Nov 28, 2012

Can you check with the spark-original-value branch too?
On Nov 27, 2012 11:48 PM, "JP Espinosa" notifications@github.com wrote:

Ex. <select name="pick" class"typo">

Tested with
Meteor 0.5.2 & devel
Mac Chrome Version 23.0.1271.91

Reproduction recipe:

git clone git://github.com/jpea/spark-patch-bug.git

And watch console


Reply to this email directly or view it on GitHubhttps://github.com//issues/512.

@jpmx
Copy link
Author

jpmx commented Nov 28, 2012

Yep, the bug is still on spark-original-value branch

@glasser
Copy link
Contributor

glasser commented Nov 28, 2012

I can reproduce this, thanks. In _copyAttributes, tgt.setAttribute(name, value) gets called with name 'class"typo"' and value ''.

I'm not really sure what to do, though. The developer had an error, and there's an exception thrown. I can try to catch the error, but then what? I'm not sure how cross-browser compatible this particular error message is, and should we just mask the error (so the developer won't notice their typo), or what?

The only real change I think is worth making in response to this error is catching and re-throwing the error in a new Error that explicitly includes the attribute name. Does that seem reasonable?

@jpmx
Copy link
Author

jpmx commented Nov 28, 2012

Totally reasonable, that would have saved hours of debugging other pieces of my code

Thanks!, and keep the great work :)

StorytellerCZ pushed a commit that referenced this issue Sep 18, 2021
…rt-2.7.0

Update eslint-plugin-import to the latest version 🚀
StorytellerCZ pushed a commit that referenced this issue Oct 1, 2021
was "make" is now "makes" in "Usually, while developing an application, it make sense to run meteor test on a second port (say 3100), while also running your main application in a separate process:"
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants