Should we remove window.blur?

[camillelamy]

The spec says "User agents are encouraged to ignore calls to this blur() method entirely." This is what Chrome does by having this method be a no-op. With the long-term goal of tightening the cross-origin WindowProxy API surface, could we remove this method entirely if user agents are supposed to do nothing when it is called?

@domenic @annevk what do you think?

[domenic]

Why is removing it better than leaving it as a no-op? Seems like that would cause needless breakage to me.

[Yay295]

I'm not entirely sure how these fit together, but would it work to not have blur() on WindowProxy but leave it on Window?

[annevk]

@Yay295 it's a bit unclear what that would mean. A web developer can never access Window directly.

[Yay295]

It seems I didn't fully understand how WindowProxy works. I agree with leaving it as it is.

Although rather than being a no-op it might be useful to have it log a warning to the console to potentially help people see it if it's being used and remove it from their code.

[camillelamy]

Could we then change the wording of the spec from "User agents are encouraged to ignore calls to this blur() method entirely." to something that is more prescriptive that this is supposed to be a no-op?

[annevk]

The blur() method steps are to do nothing.

seems reasonable to me, yeah. (In Firefox it can still do something if you flip a preference, see https://bugzilla.mozilla.org/show_bug.cgi?id=1690798, but it's not clear we want to keep that around and it's not the default configuration.)

[domenic]

Yeah such a change sounds great to me.