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

Noflo-UI changing characters when editing component #269

Closed
jpaulm opened this issue May 28, 2014 · 5 comments
Closed

Noflo-UI changing characters when editing component #269

jpaulm opened this issue May 28, 2014 · 5 comments

Comments

@jpaulm
Copy link

jpaulm commented May 28, 2014

NoFlo-UI is now changing special characters when I edit a component - @ is being replaced by ", etc. I am using Chrome under Win7. Going to try restarting machine.

@jpaulm
Copy link
Author

jpaulm commented May 29, 2014

Restarting machine fixed it. Just restarting Chrome wasn't enough!

@forresto
Copy link
Member

Sounds like a fluke? Please reopen if you can find steps to reproduce it.

@jpaulm
Copy link
Author

jpaulm commented May 31, 2014

Hi Forrest,

Just wondering - why was this closed? I would think it should be left open
as other people might stumble over it as well. Also, you may find
somewhere in your code where you are sensitive to locale or characters
sets... I don't plan to do much more work with flowhub unless some
compelling reason shows up - it just isn't relevant to the niche where I
spend most of my time, so I'm unlikely to stumble over it again! See
Oleksandr's discussion in his May 28 note to Valdimir, Henri, the two
Matts, and us!

TIA

Paul

On Thu, May 29, 2014 at 11:40 AM, Forrest Oliphant <notifications@github.com

wrote:

Closed #269 #269.


Reply to this email directly or view it on GitHub
#269 (comment).

@forresto
Copy link
Member

forresto commented Jun 2, 2014

If we can't reproduce the bug then we can't do much with it. Search works for closed issues, if somebody else finds it.

@jpaulm
Copy link
Author

jpaulm commented Jun 2, 2014

OK! Thanks, Forrest!

Regards,

Paul

On Mon, Jun 2, 2014 at 2:42 AM, Forrest Oliphant notifications@github.com
wrote:

If we can't reproduce the bug then we can't do much with it. Search works
for closed issues, if somebody else finds it.


Reply to this email directly or view it on GitHub
#269 (comment).

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