RemarkGfm display mcp url

[eleliauk]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and discussions and couldn’t find anything (or linked relevant results below)

Affected package

"remark-gfm": "^3.0.1",

Steps to reproduce

<ReactMarkdown remarkPlugins={[RemarkBreaks, plugins.RemarkMath]} rehypePlugins={[ ...rehypePlugins, rehypeHighlight, plugins.RehypeKatex, [ plugins.RehypeHighlight, { detect: false, ignoreMissing: true, }, ], ]} components={{ ...artifactComponents, a: (args) => LinkElement.Component(args, props?.sources || []), img: MarkdownImage, mark: HighlightComponent, del: StrikethroughComponent, }} linkTarget={'_blank'} > {parsedContent} </ReactMarkdown>

Actual behavior

When remarkGfm is present, output images from MCPCallElement cannot be displayed due to URL corruption. (See image below). But we need remarkGfm to render markdown tables.
refly-ai/refly#1142

Expected behavior

When remarkGfm is present, output images from MCPCallElement cannot be displayed due to URL corruption. (See image below). But we need remarkGfm to render markdown tables.refly-ai/refly#1142

Runtime

node -v # v20.19.0

Package manager

pnpm -v # 9.15.9

Operating system

macos

Build and bundle tools

No response

[wooorm]

Make a reproduction

[github-actions]

Hi! Thanks for taking the time to contribute! This has been marked by a maintainer as needing more info. It’s not clear yet whether this is an issue. Here are a couple tips:

• Spend time framing the issue! The more time you put into it, the more we will
• Often, maintainers respond with why for several back and forths; rubber duck debugging might help avoid that
• Folks posting issues sometimes fall for xy problems: asking for a certain solution instead of raising the root problem

Thanks,
— bb