If you search in Safari from Spotlight while Safari is closed, the @run-at request script will not work.

[0rodna1]

It's about this script.
https://gist.githubusercontent.com/0rodna1/0a82c96d1435f047386d1a300bb6a506/raw/03091daa2ec9850497b4289e90e0ca0b787b3390/GoogleSearch.user.js

If you search in Safari from Spotlight while Safari is opened, this script will work.

Is it the specification of declarativeNetRequest that this script doesn't work under the environment described in the title?

iOS 15.8.3
Userscripts 4.6.0-beta.4 (TestFlight)

[ACTCD]

I'm not sure how the environment you describe works, could you provide a screen recording showing your steps?

[0rodna1]

trim.19D701E4-35E7-420D-BE2B-DCF9813FE03B.MOV

[ACTCD]

Rulesets
dynamic ruleset: rules added or removed using updateDynamicRules. These rules persist across sessions and extension updates.
session ruleset: rules added or removed using updateSessionRules. These rules do not persist across browser sessions.

I just remembered that we are only registering "session ruleset" at the moment, so that may be the cause of the problem you are experiencing.

Because when opening the first page the request may be earlier than the time of the extension registers the ruleset, it will not take effect.

Using "dynamic ruleset" should solve the problem, but this will require refactoring the current logic.

Regardless, the feature isn't officially available yet, and we plan to redesign the entire DNR feature, so this may take some time.

Let me see if there's anything I can do.

[0rodna1]

I see, I understand.

I'm sorry to trouble you and I'm sorry for the inconvenience.

The @run-at request executed in this app is useful for shaping and redirecting URLs parameters.

Thank you so much for everything.

[ACTCD]

I'm sorry to say that I don't think we'll be addressing the issue right away, due to the fact that there's a lot of other high-priority work going on.

This should naturally resolve itself when we redesign the feature.

In the meantime, you should be able to temporarily circumvent the issue by:

• Use user script instead of DNR rules, although it is indeed not as efficient as DNR
• Maybe don't manually terminate Safari too often and let it keep the last session

Thanks anyway for your feedback and letting us know about the issue.

[ACTCD]

I've spent a bit of time re-reading our current logic code, and I don't think replacing it directly with dynamic ruleset under the existing logic should do any harm.

Maybe I can simply fix this issue without redesigning the entire feature.

[ACTCD]

@0rodna1 I pushed a simple refactor to solve the issue and optimize the DNR adding process.

[ACTCD]

After some testing, the solution does not work in older Safari 15.x versions. There is nothing we can do about it.

If anyone else reads this issue, please be aware of this.