xdg-desktop-portal.service and graphical-session.target ordering

[Vladimir-csp]

I see that various xdg-desktop-portal-*.service backends have After=graphical-session.target in their ordering, but xdg-desktop-portal.service does not. Is it by design?

Usually apps that require portals also start after graphical session, so xdg-desktop-portal.service de-facto also starts after, having access to WAYLAND_DISPLAY or DISPLAY vars. But nothing prevents something to interact with portals before graphical session is reached, causing xdg-desktop-portal.service to start without essential graphical session vars, which presumably can lead to situations like this.