Store and organize action views by attachment point.
Review Request #14663 — Created Oct. 31, 2025 and updated
ActionViewnow takes the attachment point that the view is placed in,
for easy lookup and for registration.The views are no longer stored in one long list. Instead, they're
organized by the attachment point. This will ultimately allow for
multiple views for the same action in different attachment points, and
to enable looking up the correct action within the right attachment
point.
Unit tests passed.
Tested that all actions, including menus and Quick Access actions,
all worked and expected.Tested that Quick Access actions could be customized.
| Summary | ID |
|---|---|
| 0acd57412d565c59c180330c9250261a7dc23cd2 |
| Description | From | Last Updated |
|---|---|---|
|
This needs a "Version Changed" block. |
|
|
|
I'm not sure I have all your changes in my head at the same time, so it's possible that this … |
|
|
|
This needs to be added to the Args section. |
|
|
|
It might be nice to fail more gracefully if attachmentPointID is not a valid key. |
|
|
|
It might be nice to fail more gracefully if attachmentPointID is not a valid key. Right now the call to … |
|
|
|
Should we |escapejs this? I guess there could be a scenario where a malicious action author sets the attachment_point_id to … |
|
-
-
-
I'm not sure I have all your changes in my head at the same time, so it's possible that this is addressed in a different change, but I see that
MenuActionViewcallspage.getActionView()with just the child ID, and there's nothing about that in this change. Is that changed elsewhere? -
-
It might be nice to fail more gracefully if
attachmentPointIDis not a valid key. Right now the call to_.filterwill probably error out.