Where does my question go / end up and how will I find the answer?

When it comes to interpreting words and scope, would the screenshot below also fall under "visual bug" and not be just a Parsoid rendering issue?:

In T363484#11015070, @cscott wrote:

Current patch demo is at https://649538b6c5.catalyst.wmcloud.org/wiki/New%20York%20City and is ready for review. I had to make a few tweaks to the design to accomodate the selected backend (posting to a talk page). In particular, I needed to provide a topic for the post and also to inform the user of the page where the message would be/was posted.

Hiya - I've revised the mocks and link to a prototype in the description to account for the reporiting flow requiring a page subject where the message will be posted, as well progress and thanks instead of a message toast.

Key updates/changes to the patchdemo include:

UI	Expected	Actual
Reporting dialog		design revisions
Progress indicator		design revisions
Thanks message		LGTM
Report link hover		low-prio

• Reporting dialog:
  • Use the subtitle prop for the "This page was rendered in Parsoid, which may..." text under the dialog title
  • Incorporate the posted subject title as the label above the text area (instead of a read-only field)
  • Put the "Your feedback was will be added to...." text into the footer-text slot instead of using an inline message.
• Progress interstitial
  • Put the Progressindicator upon submit into the permanent action section of the dialog footer instead of introducing a new dialog step/screen.
  • Keep all content in the report dialog visible, but change the "Submit" button to disabled state and the make the textArea read-only.
• Report visual bug tooltip Finally, it was expected in Matthew's mocks an inclusion of an info icon and tooltip on the link to report, but also fine to leave it if this is overkill

Two additional overarching expectations I wanted to confirm:

1. This reporting feature is only for logged in users, as I do not think it makes sense to create a temp account for the sake of reporting potential bugs.
2. The feature will be on mobile as well (see flow in the description).

Change #1170511 had a related patch set uploaded (by C. Scott Ananian; author: C. Scott Ananian):

[mediawiki/extensions/ParserMigration@master] Turn off old indicator and user notice; turn on Report Visual Bug.

https://gerrit.wikimedia.org/r/1170511

Change #1165566 had a related patch set uploaded (by C. Scott Ananian; author: C. Scott Ananian):

[mediawiki/extensions/ParserMigration@master] Create "report visual bug" dialog

https://gerrit.wikimedia.org/r/1165566

I've updated the patch demo to match the new mocks. Some responses:

• There's also an "error" state if the attempt to post the report failed. Try logging on to patch demo as the blocked user Mallory (same password) to see this behavior.
• I hadn't really thought about logged-in vs other users other than from a potential spam perspective. Right now I've added an additional configuration variable to control whether logged-out users are allowed to use the tool. If they are not (the default) "Report Visual Bug" is a static link to the feedback page; the user could presumably add a comment there manually if they are sufficiently motivated.
• I've tested on mobile and things should work well there now.
• I rather expected the stackedActions property of Dialog to be responsive to window width by default. However, code search doesn't seem to indicate any users of this property yet. I implemented the transition from horizontal to stacked buttons at window.innerWidth of 400, which seemed to match your screenshots. Is there an "official" number for where the conversion to stacked buttons should take place?

Change #1170549 had a related patch set uploaded (by C. Scott Ananian; author: C. Scott Ananian):

[operations/mediawiki-config@master] Enable the "Report Visual Bug" feature of Extension:ParserMigration

https://gerrit.wikimedia.org/r/1170549

Change #1165566 merged by jenkins-bot:

[mediawiki/extensions/ParserMigration@master] Create "report visual bug" dialog

https://gerrit.wikimedia.org/r/1165566

Change #1170549 merged by jenkins-bot:

[operations/mediawiki-config@master] Enable the "Report Visual Bug" feature of Extension:ParserMigration

https://gerrit.wikimedia.org/r/1170549

Mentioned in SAL (#wikimedia-operations) [2025-07-23T20:21:35Z] <cscott@deploy1003> Started scap sync-world: Backport for [[gerrit:1170549|Enable the "Report Visual Bug" feature of Extension:ParserMigration (T365371)]]

Mentioned in SAL (#wikimedia-operations) [2025-07-23T20:23:43Z] <cscott@deploy1003> cscott: Backport for [[gerrit:1170549|Enable the "Report Visual Bug" feature of Extension:ParserMigration (T365371)]] synced to the testservers (see https://wikitech.wikimedia.org/wiki/Mwdebug). Changes can now be verified there.

Change #1172108 had a related patch set uploaded (by C. Scott Ananian; author: C. Scott Ananian):

[mediawiki/extensions/ParserMigration@wmf/1.45.0-wmf.11] Create "report visual bug" dialog

https://gerrit.wikimedia.org/r/1172108

Mentioned in SAL (#wikimedia-operations) [2025-07-23T20:32:08Z] <cscott@deploy1003> Finished scap sync-world: Backport for [[gerrit:1170549|Enable the "Report Visual Bug" feature of Extension:ParserMigration (T365371)]] (duration: 10m 32s)

Change #1172108 merged by jenkins-bot:

[mediawiki/extensions/ParserMigration@wmf/1.45.0-wmf.11] Create "report visual bug" dialog

https://gerrit.wikimedia.org/r/1172108

Mentioned in SAL (#wikimedia-operations) [2025-07-23T20:34:35Z] <cscott@deploy1003> Started scap sync-world: Backport for [[gerrit:1172108|Create "report visual bug" dialog (T365371)]], [[gerrit:1165094|Disable ParserMigration indicator and user notice (T363484 T363472)]]

Mentioned in SAL (#wikimedia-operations) [2025-07-23T20:58:49Z] <cscott@deploy1003> cscott: Backport for [[gerrit:1172108|Create "report visual bug" dialog (T365371)]], [[gerrit:1165094|Disable ParserMigration indicator and user notice (T363484 T363472)]] synced to the testservers (see https://wikitech.wikimedia.org/wiki/Mwdebug). Changes can now be verified there.

Mentioned in SAL (#wikimedia-operations) [2025-07-23T21:15:32Z] <cscott@deploy1003> Finished scap sync-world: Backport for [[gerrit:1172108|Create "report visual bug" dialog (T365371)]], [[gerrit:1165094|Disable ParserMigration indicator and user notice (T363484 T363472)]] (duration: 40m 57s)

Latest design review (using wikivoyage):

Expected	Actual	Review note
1. Add a link to "report visual bug" in the tools menu
Desktop (with tooltip)		tooltip uses native browser instead. this is fine.
Mobile F62763350 [revised mock]		block instead of icon. Apologies the original mock did not show the intended which should be cdxIconFeedback from codex
2. Select opens a form within a dialog to report potential parsoid-related problems
Desktop		Looks good to me.
Mobile		LGTM
**3. Submit progress state
Desktop		LGTM
Mobile		FOUC on the cancel button. Low prio fix though, would accept if you want to jog on.
**4. Thank you confirmation
Desktop		Uses progressive instead of neutral button. Also low prio fix.
Mobile		Uses progressive instead of neutral button. Also low prio fix.
**5. Logged out - no reporting link or flow available
Desktop		Reporting link is still showing in the tools menu for logged out users
Mobile		LGTM

Change #1172707 had a related patch set uploaded (by C. Scott Ananian; author: C. Scott Ananian):

[mediawiki/extensions/ParserMigration@master] Report Visual Bug: address design feedback

https://gerrit.wikimedia.org/r/1172707

I'm having trouble reproducing the FOUC, but the above patch should address all the other feedback.

Change #1172707 merged by jenkins-bot:

[mediawiki/extensions/ParserMigration@master] Report Visual Bug: address design feedback

https://gerrit.wikimedia.org/r/1172707

Thank you! I retested the issues and TLDR all looks good ...details below

Expected	Actual 25th July + notes	Actual 28th July + notes
1. Add a link to "report visual bug" in the tools menu
Desktop (with tooltip)	tooltip uses native browser instead. this is fine.	n/a
Mobile F62763350 [revised mock]	block instead of icon. Apologies the original mock did not show the intended which should be cdxIconFeedback from codex	LGTM
2. Select opens a form within a dialog to report potential parsoid-related problems
Desktop	Looks good to me.	n/a
Mobile	LGTM	n/a
**3. Submit progress state
Desktop	LGTM	n/a
Mobile	FOUC on the cancel button. Low prio fix though, would accept if you want to jog on.	LGTM - in rechecking I think this was not FOUC but issues with the progress message breaking the cancel and submit buttons. This is fixed with the change to stacked actions.
**4. Thank you confirmation
Desktop	Uses progressive instead of neutral button. Also low prio fix.	LGTM
Mobile	Uses progressive instead of neutral button. Also low prio fix.	LGTM
**5. Logged out - no reporting link or flow available
Desktop	Reporting link is still showing in the tools menu for logged out users	LGTM (though unable to verify on wikivoyage)
Mobile	LGTM	n/a

About parsermigration-reportbug-feedback-title: how will it work in practice on Wikimedia sites? Will the reporting be on local wikis or on a central wiki?

It is currently centralized, following the model of Visual editor's feedback link. It can be configured to have local feedback pages for certain communities, but that adds burden to our team to try to monitor them all. We'd like to try to have a single page for as long as that is workable.