惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Spread Privacy
Spread Privacy
K
Kaspersky official blog
Application and Cybersecurity Blog
Application and Cybersecurity Blog
Forbes - Security
Forbes - Security
Hacker News - Newest:
Hacker News - Newest: "LLM"
The Last Watchdog
The Last Watchdog
SecWiki News
SecWiki News
Attack and Defense Labs
Attack and Defense Labs
Google DeepMind News
Google DeepMind News
Security Archives - TechRepublic
Security Archives - TechRepublic
S
Secure Thoughts
WordPress大学
WordPress大学
Microsoft Security Blog
Microsoft Security Blog
P
Proofpoint News Feed
云风的 BLOG
云风的 BLOG
V
Visual Studio Blog
Security Latest
Security Latest
TaoSecurity Blog
TaoSecurity Blog
Cyberwarzone
Cyberwarzone
S
SegmentFault 最新的问题
Cloudbric
Cloudbric
aimingoo的专栏
aimingoo的专栏
S
Schneier on Security
N
Netflix TechBlog - Medium
MyScale Blog
MyScale Blog
T
The Blog of Author Tim Ferriss
H
Hacker News: Front Page
C
Cybersecurity and Infrastructure Security Agency CISA
小众软件
小众软件
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
AWS News Blog
AWS News Blog
AI
AI
G
GRAHAM CLULEY
IT之家
IT之家
P
Privacy & Cybersecurity Law Blog
L
Lohrmann on Cybersecurity
Last Week in AI
Last Week in AI
D
Docker
Recent Announcements
Recent Announcements
O
OpenAI News
T
Threat Research - Cisco Blogs
GbyAI
GbyAI
S
Security @ Cisco Blogs
T
Troy Hunt's Blog
C
Check Point Blog
博客园 - 三生石上(FineUI控件)
A
About on SuperTechFans
The Cloudflare Blog
阮一峰的网络日志
阮一峰的网络日志
N
News and Events Feed by Topic

Recent Commits to web-share-target:main

Refactor: remove WebIDL (#106) · w3c/web-share-target@72dd80f chore: use group option in config · w3c/web-share-target@fadadfb chore: use main branch in config · w3c/web-share-target@a7a06ec Editorial: reference Encoding's 'UTF-8' directly (#96) · w3c/web-share-target@a703396 chore: migrate to WebApps WG (#95) · w3c/web-share-target@6025309 Accessibility considerations (#88) · w3c/web-share-target@93bf095 editorial: link to urlencoded serializer (#92) · w3c/web-share-target@a8d4a5d chore: cleanup some ReSpec usage (#91) · w3c/web-share-target@b27e5a8 Update w3c.json · w3c/web-share-target@41b27b5 Long share requests may truncate with GET (#82) · w3c/web-share-target@dd4e83f Encourage redirect after POST (#80) · w3c/web-share-target@0d9d25f Remove 'early draft' wording (#79) · w3c/web-share-target@fc831cb Skip bad files entries and make accept required (#78) · w3c/web-share-target@83a63b0 Validate enctype when method is GET (#72) · w3c/web-share-target@4078bc4 Support file sharing (#53) · w3c/web-share-target@76eabad [web-share-target] Introduce Level 2 Spec (#71) · w3c/web-share-target@a5f4eb2 Potentially trustworthy origins (#69) · w3c/web-share-target@b3c4d76 Mention plan for sharing files (#65) · w3c/web-share-target@3fccfd1 Retire links to Interface document (#62) · w3c/web-share-target@5279a5a
Possibility of transferring user id (#100) · w3c/web-share-target@0782f1a
ewilligers · 2022-01-27 · via Recent Commits to web-share-target:main

This repository was archived by the owner on Jun 30, 2026. It is now read-only.

File tree

Original file line numberDiff line numberDiff line change

@@ -634,6 +634,14 @@ <h2>

634634

being transmitted to a party that does not control the origin in

635635

question, or in clear text over the network.

636636

</li>

637+

<li>A source site using Web Share API, and a receipient site using Web

638+

Share Target, could cooperate to join user ids. The source site could

639+

use `navigator.share(text: my_id_for_this_user)`, and the (user-chosen)

640+

recipient could use that information to join its own user ID with the

641+

source origin's user ID. Both sides of the transfer would need to write

642+

code to accomplish the transfer, and the user would need to pick the

643+

recipient.

644+

</li>

637645

</ul>

638646

</section>

639647

<section id="conformance"></section>

Original file line numberDiff line numberDiff line change

@@ -955,6 +955,14 @@ <h2>

955955

transmitted to a party that does not control the origin in question,

956956

or in clear text over the network.

957957

</li>

958+

<li>A source site using Web Share API, and a receipient site using Web

959+

Share Target, could cooperate to join user ids. The source site could

960+

use `navigator.share(text: my_id_for_this_user)`, and the (user-chosen)

961+

recipient could use that information to join its own user ID with the

962+

source origin's user ID. Both sides of the transfer would need to write

963+

code to accomplish the transfer, and the user would need to pick the

964+

recipient.

965+

</li>

958966

</ul>

959967

</section>

960968

<section class="appendix informative">