alt.Text(' ') not allowed anymore?
See original GitHub issueThe Tutorial `10-HeatMaps.ipynb’ contains as last example a call where the cell text is replaced by an empty string.
This errors on Python 3.6 with GH master of altair using JupyterLab/GitHub proxy extension:
alt.Chart(cars).mark_text(applyColorToBackground=True).encode(
alt.Row('Origin:O'),
alt.Column('Cylinders:O'),
alt.Color('mean(Miles_per_Gallon):Q', sort='descending', scale=alt.Scale(range=['pink', 'red'])),
alt.Text(' '),
)
FieldError: Fields/columns not found in the data: {' '}
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
There is no character limit for “alt text”: Myth Debunked!
Some people might say that alternative text for images has a 125 character limit. That's not correct.
Read more >Alt text no more than 100 characters
The text alternative for an image must be no more than 100 characters in length. A text alternative should summarize the purpose of...
Read more >Why an HTML image alt text doesn't show on hover
Reasons why an HTML image alt text does not show when hovering in Firefox, Chrome and does show in Internet Explorer with examples....
Read more >The Rules of ALT » - HTML
The alt attribute is used to assign a text alternative to an img . The alternative text is used anytime the image is...
Read more >When is it acceptable to leave the alt text empty on an HTML ...
If there is even the slightest possibility of the author having the ability to provide real alternative text, then it would not be...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The problem is that most errors that come up will not be python errors, but javascript rendering errors. Our introduction of
FieldError
in the most recent release was an attempt to move some of the (silent) javascript errors into more noticeable python-side errors; given all the problems it’s caused I think we should probably revert that change. But that will move these types of errors back to the javascript side, so CI tests won’t catch them.This is obsolete now that we’ve moved to v2.0