Skip to content

fix: editor did not unlock after websocket disconnect#8269

Merged
CurryYangxx merged 1 commit into
developfrom
fix/websocket-editor-readonly
Dec 26, 2024
Merged

fix: editor did not unlock after websocket disconnect#8269
CurryYangxx merged 1 commit into
developfrom
fix/websocket-editor-readonly

Conversation

@CurryYangxx

Copy link
Copy Markdown
Member

close #8265

@CurryYangxx CurryYangxx requested a review from a team December 25, 2024 07:27

@cwangsmv cwangsmv left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, update the editor readonly settings after readOnly property is changed

@CurryYangxx CurryYangxx merged commit f311ac2 into develop Dec 26, 2024
@CurryYangxx CurryYangxx deleted the fix/websocket-editor-readonly branch December 26, 2024 02:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

URL lock occurs after WebSocket connection and cannot be unlocked until switching requests

2 participants