Re: [csswg-drafts] [css-om-view] Window move and resize functions should be allowed to do nothing (#4728)

The CSS Working Group just discussed `[css-om-view] Window move and resize functions should be allowed to do nothing`, and agreed to the following:

* `RESOLVED: Have smfr put in a blanket MAY saying in some situations browsers can have these functions do nothing`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic:  [css-om-view] Window move and resize functions should be allowed to do nothing<br>
&lt;dael> github: 3c/csswg-drafts/issues/4728<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4728<br>
&lt;dael> smfr: CSSOM view defines moving and resizing windows, including browser windows<br>
&lt;dael> smfr: Text restricts to only do things in certain cases which basically means pop up from window.open<br>
&lt;dael> smfr: Following spec suggests window can't self resize which might be a mistake<br>
&lt;dael> smfr: Main desire for the issue is to state browsers often prevent content from moving in other conditions then those in spec. For example may be a tab. Would like to add text to say any move and reize functions may do nothing<br>
&lt;bkardell_> sgtm<br>
&lt;dael> astearns: One sgtm in IRC. Other comments or concerns?<br>
&lt;dael> heycam: To confirm restrictions on which kinds of windows is specified in spec?<br>
&lt;dael> smfr: Says window a can move or resize if window a is familiar with window b and if it's aux browsing context. No additional optout for the UA to deicde this is bad<br>
&lt;dael> Rossen_: winow.open has capability to proive desired size and location?<br>
&lt;dael> smfr: Yes, takes features including height and width it'll be opened. I don't suggest changes to that<br>
&lt;dael> florian: Are there uses that are not abuse? If they do good to ensure browsers do it when used legit.<br>
&lt;dael> smfr: There is legit use. Used to be able to click a button and open tiled windows. INternet apps that might still be common. With many browsers having tabs it doesn't make sense for page to resize window. I see this as cutting off annoying things. Not as many legit uses, but not forward looking<br>
&lt;dael> bkardell_: Even legit don't answer how to do on mobile<br>
&lt;dael> smfr: Yeah, on mobile makes no sense.<br>
&lt;dael> smfr: And browser can't distinguish legit from abuse.<br>
&lt;dael> florian: Generally I'm fine allowing browser to curtail. If there are valid reasons to keep want to make sure not breaking them<br>
&lt;dael> smfr: Would like to hear Chrome and FF behavior. Safari considers it a pop-up if it's opened with a width. That's part of loose nature of browser wanting to cut off abuse<br>
&lt;dael> astearns: Assuming other impl don't have details at hand. Anyone want to go code spelunking?<br>
&lt;dael> heycam: I can report back in issue if that's helpful<br>
&lt;dael> smfr: I don't want to spec when it's allowed, I just want an opt out in spec text<br>
&lt;dael> astearns: May opt out. And if possible to get more details in if browsers agree that's fine in the future. Blanket may for now<br>
&lt;dael> smfr: Yeah<br>
&lt;dael> heycam: Fine with a blanket may for now.<br>
&lt;dael> astearns: Prop: Have smfr put in a blanket MAY saying in some situations browsers can have these functions do nothing<br>
&lt;dael> RESOLVED: Have smfr put in a blanket MAY saying in some situations browsers can have these functions do nothing<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4728#issuecomment-582674237 using your GitHub account

Received on Thursday, 6 February 2020 00:11:52 UTC