yyqdbngt opened a new issue, #5220:
URL: https://github.com/apache/rocketmq-dashboard/issues/5220

   ### Before creating
   
   - [x] I have searched the existing issues and found no duplicate.
   - [x] I have checked the latest `rocketmq-studio` branch where this problem 
still exists.
   
   ### Bug report
   
   **Which page or component**
   
   `web/src/components/QueueBrowser.tsx` — the Queue Browser panel of the 
message page (`useQueueBrowser`, `QueueBrowserControls`, `QueueBrowserResults`).
   
   **What happened**
   
   Every user-facing string in the panel is hardcoded Chinese: the topic 
placeholder, the "加载队列" button, both empty-state hints, the "Offset 范围" and 
"操作" column titles, the "查看" action button, the "共 N 个队列,总消息量 M 条" summary, the 
"存储时间"/"大小" detail labels, the "该 offset 处无消息" placeholder, and both error 
toasts. The component never touches the translation table, so a viewer who 
switches the display language to English keeps getting Chinese on this panel — 
the same regression class the About-tab fix (#4803) and the settings-separator 
fix (#4706) closed elsewhere.
   
   **Steps to reproduce**
   
   1. Switch the display language to English.
   2. Open any instance's message page and pick the "Browse by Queue" mode.
   3. The whole panel renders in Chinese: placeholder "选择 Topic", button 
"加载队列", empty hint "选择 Topic 并点击「加载队列」…"; trigger a load failure and the toast 
is "加载队列信息失败".
   
   **Expected behaviour**
   
   The panel goes through `t()`/`translations.ts` like every other surface, 
reusing the existing keys where the text already exists 
(`messagePage.topicPlaceholder`, `messagePage.storeTime`, `messagePage.size`, 
`common.actions`, `common.view`) and adding a `queueBrowser.*` group for the 
panel-specific strings.
   
   **Environment**
   
   branch `rocketmq-studio`, commit `4ee173ad`.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to