Copying DAG ID from UI and pasting in Slack includes schedule #22320

Apache Airflow version

2.2.3

What happened

(Yes, I know the title says Slack and it might not seem like an Airflow issue, but so far this is the only application I noticed this on. There might be others.)

PR #11503 was a fix to issue #11500 to prevent text-selection of scheduler interval when selecting DAG ID. However it does not fix pasting the text into certain applications (such as Slack), at least on a Mac.

@ryanahamilton thanks for the fix, but this is fixed in the visible sense (double clicking the DAG ID to select it will now not show the schedule interval and next run as selected in the UI), however if you copy what is selected for some reason it still includes schedule interval and next run when pasted into certain applications.

I can't be sure why this is happening, but certain places such as pasting into Google Chrome, TextEdit, or Visual Studio Code it will only include the DAG ID and a new line. But other applications such as Slack (so far only one I can tell) it includes the schedule interval and next run, as you can see below:

• Schedule interval and next run not shown as selected on the DAG page:
  
• Schedule interval and next run not pasted in Google Chrome and TextEdit:
  
  
• Schedule interval and next run pasted and visible in Slack:
  

What you think should happen instead

When you select the DAG ID on the DAG page, copy what is selected, and then paste into a Slack message, only the DAG ID should be pasted.

How to reproduce

Select the DAG ID on the DAG page (such as double-clicking the DAG ID), copy what is selected, and then paste into a Slack message.

Operating System

macOS 1.15.7 (Catalina)

Versions of Apache Airflow Providers

No response

Deployment

Astronomer

Deployment details

No response

Anything else

This is something that possibly could be a Slack bug (one could say that Slack should strip out anything that is user-select: none), however it should be possible to fix the HTML layout so user-select: none is not even needed to prevent selection. It is sort of a band-aid fix.

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct