On further testing this seems to be a Chrome browser based issued. We have the same issue in the latest versions of Chrome (112.0.5615.121) ...
確定! 回上一頁