You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@texera.apache.org by "xuang7 (via GitHub)" <gi...@apache.org> on 2026/04/11 00:52:10 UTC

[I] Enable text selection on specific metadata on dataset page [texera]

xuang7 opened a new issue, #4365:
URL: https://github.com/apache/texera/issues/4365

   ### Feature Summary
   
   Currently, text on the dataset page cannot be selected or copied, including key metadata such as the dataset name, file path, and description. Users may need to copy this information for sharing or reference purposes.
   
   ### Proposed Solution or Design
   
   The root cause is the global * { user-select: none; } rule in styles.scss that disables text selection across the entire platform. The fix is to override this rule for specific metadata fields on the dataset page.
   
   ### Impact / Priority
   
   (P2)Medium – useful enhancement
   
   ### Affected Area
   
   _No response_


-- 
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: notifications-unsubscribe@texera.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Enable text selection on specific metadata on dataset page [texera]

Posted by "aglinxinyuan (via GitHub)" <gi...@apache.org>.
aglinxinyuan commented on issue #4365:
URL: https://github.com/apache/texera/issues/4365#issuecomment-4228314383

   > This global rule was introduced in #3898 , with the intention of making text non-selectable by default across the platform while allowing specific components to override that behavior when needed. @aglinxinyuan may be able to clarify the original purpose in more detail. Thanks!
   
   @xuang7 is correct that the global rule prevent accidental text selection during drag-and-drop interactions on the workflow canvas. The rule was there since very early version of Texera. The PR mentioned was just moving the rule to the global file. We should keep this rule and decide which page is selectable.


-- 
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: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Enable text selection on specific metadata on dataset page [texera]

Posted by "chenlica (via GitHub)" <gi...@apache.org>.
chenlica commented on issue #4365:
URL: https://github.com/apache/texera/issues/4365#issuecomment-4229617103

   I suggest by default we enable "selectable" as it's the norm.  For some pages, we can disable it.


-- 
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: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Enable text selection on specific metadata on dataset page [texera]

Posted by "mengw15 (via GitHub)" <gi...@apache.org>.
mengw15 closed issue #4365: Enable text selection on specific metadata on dataset page
URL: https://github.com/apache/texera/issues/4365


-- 
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: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Enable text selection on specific metadata on dataset page [texera]

Posted by "chenlica (via GitHub)" <gi...@apache.org>.
chenlica commented on issue #4365:
URL: https://github.com/apache/texera/issues/4365#issuecomment-4228126535

   Can you find the PR that introduced this feature and try to understand the reason?
   


-- 
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: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Enable text selection on specific metadata on dataset page [texera]

Posted by "aglinxinyuan (via GitHub)" <gi...@apache.org>.
aglinxinyuan commented on issue #4365:
URL: https://github.com/apache/texera/issues/4365#issuecomment-4230034912

   > I suggest by default we enable "selectable" as it's the norm.  For some pages, we can disable it.
   
   +1


-- 
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: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Enable text selection on specific metadata on dataset page [texera]

Posted by "mengw15 (via GitHub)" <gi...@apache.org>.
mengw15 commented on issue #4365:
URL: https://github.com/apache/texera/issues/4365#issuecomment-4228330307

   In this case, would it be reasonable to allow text selection across all dataset level panels to keep the behavior consistent? For example, panels like Datasets, Workflow, Compute, also panels under Admin and Hub.


-- 
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: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Enable text selection on specific metadata on dataset page [texera]

Posted by "xuang7 (via GitHub)" <gi...@apache.org>.
xuang7 commented on issue #4365:
URL: https://github.com/apache/texera/issues/4365#issuecomment-4228123501

   One possible reason for this rule could be to prevent accidental text selection during drag-and-drop interactions on the workflow canvas, to enhance the user experience. However, this also affects display-only pages like the dataset page where text selection should be allowed.


-- 
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: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Enable text selection on specific metadata on dataset page [texera]

Posted by "aglinxinyuan (via GitHub)" <gi...@apache.org>.
aglinxinyuan commented on issue #4365:
URL: https://github.com/apache/texera/issues/4365#issuecomment-4228333613

   > In this case, should we allow text selection across all dataset level panels to keep the behavior consistent? For example, panels like Datasets, Workflow, Compute, also panels under Admin and Hub.
   
   We can check what the other drag-and-drop system does.


-- 
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: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Enable text selection on specific metadata on dataset page [texera]

Posted by "mengw15 (via GitHub)" <gi...@apache.org>.
mengw15 commented on issue #4365:
URL: https://github.com/apache/texera/issues/4365#issuecomment-4228088779

   A general question: why did we choose to apply user-select: none globally in the first place? What was the reason behind that decision? Would it be possible to allow text selection globally instead? I noticed that text is also not selectable on other pages, such as Workflow and Compute. Should we make this behavior consistent across the platform?


-- 
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: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Enable text selection on specific metadata on dataset page [texera]

Posted by "xuang7 (via GitHub)" <gi...@apache.org>.
xuang7 commented on issue #4365:
URL: https://github.com/apache/texera/issues/4365#issuecomment-4228234569

   This global rule was introduced in #3898 , with the intention of making text non-selectable by default across the platform while allowing specific components to override that behavior when needed. @aglinxinyuan may be able to clarify the original purpose in more detail. Thanks!


-- 
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: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Enable text selection on specific metadata on dataset page [texera]

Posted by "mengw15 (via GitHub)" <gi...@apache.org>.
mengw15 commented on issue #4365:
URL: https://github.com/apache/texera/issues/4365#issuecomment-4228365502

   > We can check what the other drag-and-drop system does.
   
   I took a quick look at Galaxy. On its drag-and-drop canvas, components are generally not selectable, and some button text is also not selectable. However, on other pages, most text remains selectable. Within the canvas page, panels similar to property panel also allow text selection and copying.
   
   Maybe we should consider making text selectable by default globally, and then explicitly disabling selection only in places where it would interfere with interactions.
   
   Or we could first allow text selection across all panels at the dataset-page level first, to keep the behavior consistent there.


-- 
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: notifications-unsubscribe@texera.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org