How do we allow the clients to read, and understand what they could and should do to benefit then. This type stuff mY he good for people with experience but others. Who unintentionally got involved. It messes with more than their os version
On Mon, Jun 27, 2022, 5:09 PM <blink-dev@chromium.org> wrote: > blink-dev@chromium.org > <https://groups.google.com/a/chromium.org/forum/?utm_source=digest&utm_medium=email#!forum/blink-dev/topics> > Google > Groups > <https://groups.google.com/a/chromium.org/forum/?utm_source=digest&utm_medium=email/#!overview> > <https://groups.google.com/a/chromium.org/forum/?utm_source=digest&utm_medium=email/#!overview> > Today's topic summary > View all topics > <https://groups.google.com/a/chromium.org/forum/?utm_source=digest&utm_medium=email#!forum/blink-dev/topics> > > - Suggestion to stop using the term “third-party” in proposal > explainers <#m_-6505441399365095907_group_thread_0> - 2 Updates > - Intent to Experiment: Declarative Beacon API > <#m_-6505441399365095907_group_thread_1> - 1 Update > - Intent to Ship: Viewport-height client hint > <#m_-6505441399365095907_group_thread_2> - 1 Update > - Intent to Prototype: Origin-Bound Cookies > <#m_-6505441399365095907_group_thread_3> - 2 Updates > - WebView Origin Trials enabled on 103 beta > <#m_-6505441399365095907_group_thread_4> - 2 Updates > - Intent to Ship: Writable directory prompts for the File System > Access API <#m_-6505441399365095907_group_thread_5> - 1 Update > - Intent to Ship: CSS :modal Pseudo Class > <#m_-6505441399365095907_group_thread_6> - 1 Update > - Blink bug status as of 2022-06-27 > <#m_-6505441399365095907_group_thread_7> - 1 Update > > Suggestion to stop using the term “third-party” in proposal explainers > <http://groups.google.com/a/chromium.org/group/blink-dev/t/aec9b5cd2d990721?utm_source=digest&utm_medium=email> > "Šime Vidas" <sime.vi...@gmail.com>: Jun 26 07:12PM -0700 > > I was taking a look at the explainer for LazyEmbeds [1], and I thought > that > the first sentence could have been more clear if it didn’t use the terms > “third-party” and “first-party”. > ...more > <http://groups.google.com/a/chromium.org/group/blink-dev/msg/36a33d45d2bf1?utm_source=digest&utm_medium=email> > Johann Hofmann <johann...@chromium.org>: Jun 27 10:17PM +0200 > > I generally agree with Tess' document to the extent that the party terms > are currently not well suited for specification language because of their > ambiguity. You're also right that ideally ...more > <http://groups.google.com/a/chromium.org/group/blink-dev/msg/37f9efd2ae822?utm_source=digest&utm_medium=email> > Back to top <#m_-6505441399365095907_digest_top> > Intent to Experiment: Declarative Beacon API > <http://groups.google.com/a/chromium.org/group/blink-dev/t/55de914c87f19226?utm_source=digest&utm_medium=email> > Caleb Raitto <carai...@google.com>: Jun 27 11:09AM -0700 > > Hi, I filed https://github.com/darrenw/docs/issues/3 about a time limit > on > the duration from bfcache page freeze to beacons being sent -- could you > PTAL? > > Thanks, > -Caleb > > ...more > <http://groups.google.com/a/chromium.org/group/blink-dev/msg/37f99107a22e2?utm_source=digest&utm_medium=email> > Back to top <#m_-6505441399365095907_digest_top> > Intent to Ship: Viewport-height client hint > <http://groups.google.com/a/chromium.org/group/blink-dev/t/d7b677d342b1ad03?utm_source=digest&utm_medium=email> > Max Curran <curran...@google.com>: Jun 27 01:15PM -0700 > > Contact emails > > ryanst...@chromium.org, curran...@chromium.org > > Explainer > > > https://github.com/WICG/responsive-image-client-hints/blob/master/Viewport-Height-Explainer.md > > Specification > ...more > <http://groups.google.com/a/chromium.org/group/blink-dev/msg/37f7598896ce8?utm_source=digest&utm_medium=email> > Back to top <#m_-6505441399365095907_digest_top> > Intent to Prototype: Origin-Bound Cookies > <http://groups.google.com/a/chromium.org/group/blink-dev/t/c4a4de9bf5f62d4f?utm_source=digest&utm_medium=email> > g16 <g16g16...@gmail.com>: Jun 27 01:00AM +0900 > > Hi > > I have a question about cross-scheme cookies. > > I've heard that a few people handle cookies on the server side when > upgrading to WebSockets. > > Developer cannot be opt-out scheme bindings. ...more > <http://groups.google.com/a/chromium.org/group/blink-dev/msg/36a3cbf550a86?utm_source=digest&utm_medium=email> > Steven Bingler <bing...@chromium.org>: Jun 27 10:12AM -0700 > > Hello, > > That's a good question. > > > Developer cannot be opt-out scheme bindings. then, will not cookies set > by https://example.com not be sent to wss://example.com ? > Cookies will be sent in your ...more > <http://groups.google.com/a/chromium.org/group/blink-dev/msg/3757da6d3b9c6?utm_source=digest&utm_medium=email> > Back to top <#m_-6505441399365095907_digest_top> > WebView Origin Trials enabled on 103 beta > <http://groups.google.com/a/chromium.org/group/blink-dev/t/a5bf94b32b231cc1?utm_source=digest&utm_medium=email> > Peter Birk Pakkenberg <pb...@google.com>: Jun 27 09:51AM +0100 > > Hi Christian, > > Certainly. > The answer is currently yes and no, respectively. Webview shares the > android build target, so they are tied together right now. > > Do you have a specific trial that you ...more > <http://groups.google.com/a/chromium.org/group/blink-dev/msg/35a2e2d011586?utm_source=digest&utm_medium=email> > Christian Biesinger <cbiesin...@chromium.org>: Jun 27 11:53AM -0400 > > Yes, my concern is the "FedCm" origin trial. > > In particular, webview will not have an implementation on the embedder > side, so the API will not work. But since the origin trial code does not > ...more > <http://groups.google.com/a/chromium.org/group/blink-dev/msg/371330f803deb?utm_source=digest&utm_medium=email> > Back to top <#m_-6505441399365095907_digest_top> > Intent to Ship: Writable directory prompts for the File System Access API > <http://groups.google.com/a/chromium.org/group/blink-dev/t/82f965e47c91e69b?utm_source=digest&utm_medium=email> > Austin Sullivan <asu...@google.com>: Jun 27 10:40AM -0400 > > PR is landed > > ...more > <http://groups.google.com/a/chromium.org/group/blink-dev/msg/36d3588e630ba?utm_source=digest&utm_medium=email> > Back to top <#m_-6505441399365095907_digest_top> > Intent to Ship: CSS :modal Pseudo Class > <http://groups.google.com/a/chromium.org/group/blink-dev/t/9061d506d552d57f?utm_source=digest&utm_medium=email> > Jihwan Kim <bluewhale.m...@gmail.com>: Jun 27 06:20AM -0700 > > I have updated the I2S contents including explainer, vendor signals those > are commented. > We may now progress this I2S. > thanks. > > 2022년 6월 24일 금요일 오전 4시 2분 49초 UTC+9에 Chris ...more > <http://groups.google.com/a/chromium.org/group/blink-dev/msg/368d8b99ec9b4?utm_source=digest&utm_medium=email> > Back to top <#m_-6505441399365095907_digest_top> > Blink bug status as of 2022-06-27 > <http://groups.google.com/a/chromium.org/group/blink-dev/t/8cf0b1e31d904948?utm_source=digest&utm_medium=email> > tk...@chromium.org: Jun 26 04:50PM -0700 > > Blink bug status as of 2022-06-27 > > Component Open Slow Triage Pri-0/1 > > ⭐ No owner Oldest > > Whole Blink 16,976 (+60) 72,998 (+3,014) 1,076 (-87) 1,065 (+43) 305 Jan > 2015 > > Uncategorized 3 (-1) ...more > <http://groups.google.com/a/chromium.org/group/blink-dev/msg/33ca514e2e205?utm_source=digest&utm_medium=email> > Back to top <#m_-6505441399365095907_digest_top> > You received this digest because you're subscribed to updates for this > group. You can change your settings on the group membership page > <https://groups.google.com/a/chromium.org/forum/?utm_source=digest&utm_medium=email#!forum/blink-dev/join> > . > To unsubscribe from this group and stop receiving emails from it send an > email to blink-dev+unsubscr...@chromium.org. > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL3UEnwy9MF0e%3DFtpr2Oxj8Tbzya5A0NL7Y0fvbPZY0d5PD33w%40mail.gmail.com.
