The Sales assistant ignores an attached photo in WebKit
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start with the E2E test WebAiChatbotAttachmentTests.Assistant_Should_DescribeAProductImage_TheUserAttached and the attachment step that waits for the composer and Send button, then run it under WebKit to reproduce the failure. Next, trace whether the uploaded .webp reaches the chat request and the model call, since the server log is empty for that window. Done means the WebKit run identifies the car in the image, or the missing step is found and fixed with the Chromium and Firefox runs still passing.
Written by the indexing model from the issue text.
Description
In WebKit, the Sales demo's assistant answers as if a photo attached to the chat wasn't there. The E2E test WebAiChatbotAttachmentTests.Assistant_Should_DescribeAProductImage_TheUserAttached attaches a product photo (a Benz EQB SUV, .webp, from the demo's own attachment url), waits until it shows in the composer and Send is enabled, and asks "What car is in this picture?". In WebKit the answers are:
- "I can help identify or compare cars sold in the Boilerplate app, but I can't identify a car from an image."
- "Identifying a car in an image is outside what I can help with; I can help you find or compare cars sold in the Boilerplate app."
It failed all 6 attempts in two runs on 2026-11-15, on WebKit through the mac's Playwright server, against sales.bitplatform.dev at 325.33.46. The same test passed on Chromium and Firefox in the same run. The server's Application log has nothing for the upload or the chat in that window, so it isn't yet known whether the photo reaches the model.
- Dominant language
- C#
- Stars
- 1.4k
- Forks
- 264
- Avg merge
- 8h 58m
- Merged PRs (30d)
- 579
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bitfoundation/bitplatform
-
area / templates
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
bitfoundation/bitplatform#15109 ·
Maintainers usually reply within 1 day
-
area / templates
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
bitfoundation/bitplatform#15108 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
bitfoundation/bitplatform#15051 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 12/100
bitfoundation/bitplatform#15100 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
bitfoundation/bitplatform#15097 ·
Maintainers usually reply within 1 day
All issues in bitfoundation/bitplatform
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Natvs/Nt.Automaton#33 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
a-corriger documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
christian-raj/S-Aloha#312 ·
-
ready-for-agent tech-debt
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
DigiBanks99/menlo#640 ·
Maintainers usually reply within 1 day
-
ci
Difficulty 1/5 Under an hour Newbie friendliness 62/100
OpenTabletDriver/OpenTabletDriver#5283 ·
Maintainers usually reply within 3 days