question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

4.11.0 minimal bundle => No renderer for attachment for screen reader of type XY

See original GitHub issue

Screenshots

image

image

Version

4.11.0 / NPM (‘botframework-webchat/lib/index-minimal’) / (but it also happening using CDN minimal bundle)

Describe the bug

We’re using the minimal bundle for our webchat. We’re rendering all of the messages by our self. Since we’ve updated to 4.11.0, all activities are still rendered as before, but there are errors in the console about missing renderers for screen readers, like:

ErrorBox.js?ffa8:44 Error: No renderer for attachment for screen reader of type "application/vnd.microsoft.card.hero"

Steps to reproduce

  1. Run this sample 01.getting-started/b.minimal-bundle
  2. Open console in developer tools
  3. Type “help”
  4. Observe errors

Expected behavior

I expect to have one of the following:

  • renderers in that bundle
  • no renderers but no errors
  • documented a way how to suppress/ignore errors from missing renderers => any idea to work around the issue?

[Bug]

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:6 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
corinagumcommented, Dec 4, 2020

Hi @martinoss, thanks for filing this issue. I have a repro of this, and will investigate the problem. I don’t think I’ll get an answer to this thread today, but I will get it in as soon as possible early next week.

0reactions
corinagumcommented, Jan 14, 2021
  1. change to warning, not error
  2. suppress warning? React props.ref - console log ==> warning, align with this behavior / production
    1. npm build - production vs start (dev)
    2. if suppressable, write sample
    3. default props (not style options)
    4. suppress red box in production & no announcement in screenreader (when WC dep in CRA)
  3. Sample for suppressing warnings (from test code)
  4. dev mode, non-suppressed - have screenreader renderer saying activity could not be rendered
Read more comments on GitHub >

github_iconTop Results From Across the Web

Unreal Engine 4.11 Released!
Several new rendering and animation features focused on rendering realistic characters are in 4.11, as are new audio features and tools ...
Read more >
jogl Changes [Jenkins] - JogAmp
Bug 1017 - TextureIO.write(Texture, File) throws GLException Not a GL2 (commit: ... Graph/Text: Prepare unit tests for font rendering validation (WIP) ...
Read more >
[opensuse-arm] New Tumbleweed snapshot 20191018 ...
- Use autosetup and cmake_build macros. - Stop passing -DCMAKE_SKIP_RPATH=OFF and - DCMAKE_BUILD_WITH_INSTALL_RPATH=ON to cmake, no longer needed. - Replace gcc ...
Read more >
Table 11 :: OIN Linux System - Open Invention Network
Any changes not permitted by the configuration file are reported. ... used such as tools such as screen readers, magnifiers, and alternative input...
Read more >
node.js - Adapative card not rendering properly - Stack Overflow
when we use minimal bundle, which doesn't include Adaptive Cards. we need to use the full bundle if you want to use Adaptive...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found