Share page report abuse dialog: Submit button should be rightmost action

Still repros
Recommendation for Triage
Issue Type: bug
Status: info-complete
Label(s): sharepage, ui design
Duplicate Issue(s): No duplicate issue found
Likely Related: No related issue found
Suggested Priority: P3
Complexity: low
Copilot Agent Ready: β Yes
Recommendations for Assignee
Analysis
This is a UI/UX inconsistency issue where the "Submit" button appears on the left side of the dialog instead of the right, violating standard UI conventions where the primary action should be the rightmost button. The screenshot clearly shows the problem in the report abuse dialog on the share page. This is a straightforward button order fix that improves user experience by following established UI patterns.
Duplicate & Related Issues
Duplicates:
- No duplicates found via search
Related Issues:
- No closely related issues found, though there are several other sharepage and UI design issues logged separately (#5082 about "Continue" button text, #6518 about icon inconsistency, #6642 about missing share button)
Location Hints
Based on code search, the report abuse functionality is defined in the pxt-core repository (microsoft/pxt), not pxt-arcade:
../pxt/docfiles/abuse.html- Contains the abuse report modal HTML structure with button order that needs to be fixed. The buttons are currently ordered as:(div class="ui ok button violet")Submit(/div)followed by(div class="ui cancel button")Cancel(/div). These should be swapped so Cancel is first and Submit is last (rightmost).
Note: This file is in the pxt-core repository at ../pxt/docfiles/abuse.html. While the issue was filed in pxt-arcade, the fix needs to be made in the microsoft/pxt repository. This is acceptable as per the workspace instructions - pxt-core issues can be triaged and fixed through the pxt-arcade repository workflow.
Next Steps
Copilot Coding Agent Assessment: β Yes, ready as-is
Reasoning: This is a simple HTML/DOM structure change with a clear fix - swap the order of two button elements in the abuse.html file. The issue is well-documented with a screenshot, the affected code has been located, and the change is isolated to button ordering. This is an ideal low-complexity task suitable for automated fixing.
π΄ββ οΈ Ahoy! This treasure was crafted by pxt-arcade Issue Triage Assistant fer issue #5518 πΊοΈ