Revert "510322-ai-resolution-on-the-mr-widget-use-mutation-observer-for-scroll-trigger"

added Pick into auto-deploy master:broken pipelineexpedited priority1 regression:17.9 severity1 labels

requested review from @mchacon3

added Quality label

Proper labels assigned to this merge request. Please ignore me.

@jennykim-gitlab - please see the following guidance and update this merge request.

	1 Error
	Please add typebug typefeature, or typemaintenance label to this merge request.

added frontend label

	1 Warning
	This merge request does not refer to an existing milestone.

	1 Message
	This merge request includes changes to Vue files that have both CE and EE versions.

Vue `<template>` in CE and EE

Some Vue files in CE have a counterpart in EE. (For example, path/to/file.vue and ee/path/to/file.vue.)

When run in the context of CE, the <template> of the CE Vue file is used. When run in the context of EE, the <template> of the EE Vue file is used.

It's easy to accidentally make a change to a CE <template> that should appear in both CE and EE without making the change in both places. When this happens, the change only takes effect in CE.

The following Vue files were changed as part of this merge request that include both a CE and EE version of the file:

ee/app/assets/javascripts/vue_merge_request_widget/widgets/security_reports/mr_widget_security_reports.vue

If you made a change to the <template> of any of these Vue files that should be visible in both CE and EE, please ensure you have made your change to both versions of the file.

A better alternative

An even better alternative is to refactor this component to only use a single template for both CE and EE. More info on this approach here: https://docs.gitlab.com/ee/development/ee_features.html#template-tag

Reviewer roulette

Category	Reviewer	Maintainer
frontend	`@fernanda.toledo` (UTC-8, 3 hours behind author)	`@svedova` (UTC+1, 6 hours ahead of author)

Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

approved this merge request

added typebug label

resolved all threads

enabled automatic add to merge train when checks pass

mentioned in merge request !177883 (merged)

mentioned in incident gitlab-com/gl-infra/production#19229 (closed)

changed the description

mentioned in issue gitlab-com/gl-infra/on-call-handovers#5740 (closed)

approved this merge request

started a merge train

removed this merge request from the merge train because the pipeline did not succeed. Learn more.

enabled automatic add to merge train when checks pass

started a merge train

merged

mentioned in commit 604ea2e2

Successfully picked into 17-9-auto-deploy-2025020323.

This merge request will receive additional notifications as it's deployed. You can also use the following chatops command to check its status: /chatops run auto_deploy status https://gitlab.com/gitlab-org/gitlab/-/merge_requests/180090

Successfully picked into 17-9-auto-deploy-2025020400.

This merge request will receive additional notifications as it's deployed. You can also use the following chatops command to check its status: /chatops run auto_deploy status https://gitlab.com/gitlab-org/gitlab/-/merge_requests/180090