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.

Sign up for GitHub

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

Jump to bottom

Type "<" and ">" will cause incorrect format #30

Closed
iwang opened this issue Nov 27, 2013 · 6 comments
Closed

Type "<" and ">" will cause incorrect format #30

iwang opened this issue Nov 27, 2013 · 6 comments
Assignees
@SimeonC
Milestone
1.1.2

Comments

@iwang
Copy link

iwang commented Nov 27, 2013

If you type "<" or ">" then toggle to source view then back, the format will all go wrong.
@SimeonC
Copy link
Collaborator

SimeonC commented Nov 27, 2013

Hi, Could you be a bit more specific please. Also are you using v1.1.0 or the v1.0.2 on textangular.com?

@iwang
Copy link
Author

iwang commented Nov 28, 2013

I mean v1.1.0, sorry for missing that. Actually I also tried on http://www.textangular.com/, the same problem. Btw, adding "<" in different position of the content will cause different behavior.
I inserted "<" before the first character, click source button and click again, all content became bold.

@SimeonC
Copy link
Collaborator

SimeonC commented Nov 28, 2013

OK, well that's the first potential problem out of the way!
I have a codepen up here: http://codepen.io/SimeonC/pen/ef5d215d7968fd58145c9980c66c7251
Can you try and replicate it in there, then tell me how to do it and what browser you are using please.
Once you've given me that I'll have a shot at fixing it as in my browser it doesn't happen!

@SimeonC
Copy link
Collaborator

SimeonC commented Nov 28, 2013

Ah, never mind - I've spotted the problem. I'll let you know when I've figured out how to fix it.

SimeonC pushed a commit to SimeonC/textAngular that referenced this issue Nov 29, 2013
Pending Fix for issues textAngular#30, textAngular#35.
0bf63fe
@SimeonC
Copy link
Collaborator

SimeonC commented Nov 29, 2013

I've got a fix for this it took some work to get around it but I think I've got the whole thing done.
Could you test your issue on the version over on my fork and let me know if that fixes it please.

@ghost ghost assigned SimeonC Nov 29, 2013
@SimeonC SimeonC mentioned this issue Dec 5, 2013
Closed
SimeonC pushed a commit to SimeonC/textAngular that referenced this issue Dec 5, 2013
Fixes for: textAngular#38, textAngular#29, textAngular#35, textAngula…
e84d285 
…r#30, textAngular#19

Updates the fix introduced in textAngular#5 to be more specific and less of a catch all.
Changed version to v1.1.2
@SimeonC
Copy link
Collaborator

SimeonC commented Dec 5, 2013

I'm going to close this with the release of the 1.1.2-alpha. If that doesn't fix it for you please do re-open the issue.

@SimeonC SimeonC closed this as completed Dec 5, 2013
netbubu17 pushed a commit to netbubu17/textAngular that referenced this issue Dec 19, 2013
Pending Fix for issues textAngular#30, textAngular#35.
8db8f41
netbubu17 pushed a commit to netbubu17/textAngular that referenced this issue Dec 19, 2013
Fixes for: textAngular#38, textAngular#29, textAngular#35, textAngula…
373a90d 
…r#30, textAngular#19

Updates the fix introduced in textAngular#5 to be more specific and less of a catch all.
Changed version to v1.1.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SimeonC SimeonC

Labels
None yet
Projects
None yet
Milestone
1.1.2
Development

No branches or pull requests
2 participants
@SimeonC @iwang