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

Jupyter Viewer: ellipsis character breaks the component #2

Open
labarba opened this issue Sep 9, 2018 · 5 comments
Open

Jupyter Viewer: ellipsis character breaks the component #2

labarba opened this issue Sep 9, 2018 · 5 comments

Comments

@labarba
Copy link
Member

labarba commented Sep 9, 2018

It looks like the viewer is unable to display content from a notebook when a cell contains the ellipsis character, u'\u2026' —see screenshot.

screen shot 2018-09-09 at 5 19 13 pm

@labarba
Copy link
Member Author

labarba commented Sep 9, 2018

For now, since I want to finish this course, I will edit the source notebook and remove the character. But this should be fixed or it may trip others in the future.

Course I'm working on:
https://openedx.seas.gwu.edu/courses/course-v1:GW+EngComp2+2018/

@labarba
Copy link
Member Author

labarba commented Nov 6, 2018

I used the em-dash (—) character in one End Tag, and the component breaks, too.

@geoff-va
Copy link
Collaborator

geoff-va commented Mar 8, 2019

Hi @labarba,

Can you confirm if this is still an issue, or point me to a notebook that has this issue?

I just tried the following commit which looks like it has the ellipsis character in the Bubble Chart section and it looks like it's rendering properly.

Thanks!

@labarba
Copy link
Member Author

labarba commented Aug 27, 2019

I just tried to load a notebook with a horizontal ellipsis in the string for the "Start tag" and it fails.

The error says:

WE'RE HAVING TROUBLE RENDERING YOUR COMPONENT

Students will not be able to access this component. Re-edit your component to fix the error.

Error: 'ascii' codec can't encode character u'\u2026' in position 26: ordinal not in range(128)

@labarba
Copy link
Member Author

labarba commented Aug 27, 2019

The only option at that point is to delete the Unit, because it is not possible to edit the component any longer.

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