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

Get TypeError when running forte/examples/visualize #198

Open
mylibrar opened this issue Jun 23, 2021 · 2 comments
Open

Get TypeError when running forte/examples/visualize #198

mylibrar opened this issue Jun 23, 2021 · 2 comments

Comments

@mylibrar
Copy link
Collaborator

Describe the bug
Get a TypeError when running the examples in forte/examples/visualize.

TypeError: undefined is not an object (evaluating 'o.position.rects[0].x')

To Reproduce
Steps to reproduce the behavior:
1.

git clone https://github.com/asyml/forte.git
cd forte/examples/visualize
cat README.md
  1. Follow the steps described in the README.md file and you will get a terminal prompt like:
Enter your query here: 
  1. Copy the following text and paste it into terminal.
Forte provides a platform to assemble state-of-the-art NLP and ML technologies in a highly-composable fashion, including a wide spectrum of tasks ranging from Information Retrieval, Natural Language Understanding to Natural Language Generation.

Press return on keyboard and a Stave web page should be popped out, from which you can view the text you just entered.
4. Click the radio button of Token on the left panel and an error message will show in browser console.

TypeError: undefined is not an object (evaluating 'o.position.rects[0].x')

Expected behavior
No error should appear and Stave should correctly show the Token annotations.

Screenshots
image
image

Environment (please complete the following information):

  • OS: macOS
  • Version 11.4

Additional context
Add any other context about the problem here.

@hepengfe
Copy link
Collaborator

I found that it's browser-specific. Only Safari has the issue, and chrome doesn't.

@hunterhector
Copy link
Member

I found that it's browser-specific. Only Safari has the issue, and chrome doesn't.

Hmm, good to know, I think we can create a issue after we finish the upgrade (with browser type/version etc.)

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

3 participants