w3c/beacon issues and pull requests

#82 - Chrome, Safari and Firefox behave differently when beacon blocked by CSP

Issue - State: open - Opened by chernodub 10 months ago - 1 comment

#81 - Remove deps section, properly cross-reference links

Pull Request - State: closed - Opened by clelland over 2 years ago

#80 - Update process

Pull Request - State: closed - Opened by clelland over 2 years ago - 3 comments

#79 - Duplicate, vague, and monkeypatching normative requirements

Issue - State: open - Opened by domenic over 2 years ago

#78 - Is "entry setings object" correct?

Issue - State: closed - Opened by domenic over 2 years ago - 1 comment

#77 - References terms from Page Visibility, which is a discontinued draft

Issue - State: closed - Opened by domenic over 2 years ago - 2 comments

#76 - Setup auto publishing

Issue - State: closed - Opened by yoavweiss almost 3 years ago - 9 comments

#75 - Adjust resource-timing reporting to fetch refactor

Pull Request - State: closed - Opened by noamr almost 3 years ago

#74 - Editorial: align with fetch algorithm rename

Pull Request - State: closed - Opened by noamr about 3 years ago

#73 - Account for fetch algorithm rename

Issue - State: closed - Opened by noamr about 3 years ago

#72 - Option to request beacon be compressed

Issue - State: open - Opened by nicjansma about 3 years ago - 9 comments

#71 - Report timing for beacon when fetch is done

Pull Request - State: closed - Opened by noamr over 3 years ago

#70 - Integrate with Resource Timing

Issue - State: closed - Opened by noamr over 3 years ago

#69 - Fix up editor data

Pull Request - State: closed - Opened by jyasskin over 3 years ago

#68 - Drop dependencies section

Issue - State: closed - Opened by marcoscaceres over 3 years ago - 1 comment

#67 - Switch to GitHub action

Pull Request - State: closed - Opened by plehegar over 3 years ago
Labels: w3c

#66 - Set the keepalive flag when extracting the body

Pull Request - State: closed - Opened by ricea about 5 years ago

#65 - Add conformance section

Pull Request - State: closed - Opened by tidoust about 5 years ago

#64 - When can Beacon support the GET method?

Issue - State: closed - Opened by berwin over 6 years ago - 2 comments

#64 - When can Beacon support the GET method?

Issue - State: closed - Opened by berwin over 6 years ago - 2 comments

#63 - navegator.sendBeacon cookie visibility question.

Issue - State: closed - Opened by easher over 6 years ago - 4 comments

#62 - Fixed typos: visiblityState -> visibilityState

Pull Request - State: closed - Opened by zurmuehl almost 7 years ago - 1 comment

#62 - Fixed typos: visiblityState -> visibilityState

Pull Request - State: closed - Opened by zurmuehl almost 7 years ago - 1 comment

#61 - Typo in Example 1 code

Issue - State: closed - Opened by zurmuehl almost 7 years ago - 5 comments

#60 - Firefox, Chrome and Edge all fail http referrer test

Issue - State: closed - Opened by toddreifsteck almost 7 years ago - 5 comments

#59 - beacon-navigate is broken

Issue - State: closed - Opened by toddreifsteck almost 7 years ago - 1 comment

#58 - Resource Timing + beacon test

Issue - State: closed - Opened by toddreifsteck almost 7 years ago - 2 comments

#58 - Resource Timing + beacon test

Issue - State: closed - Opened by toddreifsteck almost 7 years ago - 2 comments

#57 - Typo in Privacy and Security

Issue - State: closed - Opened by JosephPecoraro over 7 years ago - 1 comment

#57 - Typo in Privacy and Security

Issue - State: closed - Opened by JosephPecoraro over 7 years ago - 1 comment

#56 - Typo in Processing Model - fetch step

Issue - State: closed - Opened by JosephPecoraro over 7 years ago - 1 comment

#56 - Typo in Processing Model - fetch step

Issue - State: closed - Opened by JosephPecoraro over 7 years ago - 1 comment

#55 - Typo in Introduction note

Issue - State: closed - Opened by JosephPecoraro over 7 years ago

#54 - cleanup processing section

Pull Request - State: closed - Opened by igrigorik over 7 years ago - 4 comments

#53 - corsMode calculation in the "Processing Model" section is broken

Issue - State: closed - Opened by tyoshino over 7 years ago - 1 comment

#52 - remove referrer resource

Pull Request - State: closed - Opened by siusin over 7 years ago - 2 comments

#52 - remove referrer resource

Pull Request - State: closed - Opened by siusin over 7 years ago - 2 comments

#51 - Remove referrer source definition + HTML5.2 dep

Issue - State: closed - Opened by igrigorik over 7 years ago - 2 comments

#51 - Remove referrer source definition + HTML5.2 dep

Issue - State: closed - Opened by igrigorik over 7 years ago - 2 comments

#50 - Clean up the Dependencies section - fix #47

Pull Request - State: closed - Opened by siusin over 7 years ago - 13 comments

#50 - Clean up the Dependencies section - fix #47

Pull Request - State: closed - Opened by siusin over 7 years ago - 13 comments

#49 - How important is it for sendBeacon() to follow redirects?

Issue - State: closed - Opened by cdumez over 7 years ago - 12 comments

#49 - How important is it for sendBeacon() to follow redirects?

Issue - State: closed - Opened by cdumez over 7 years ago - 12 comments

#48 - Should sendBeacon set the FetchRequest's cacheMode to "no-cache"?

Issue - State: closed - Opened by cdumez over 7 years ago - 4 comments

#48 - Should sendBeacon set the FetchRequest's cacheMode to "no-cache"?

Issue - State: closed - Opened by cdumez over 7 years ago - 4 comments

#47 - Editorial cleanup

Issue - State: closed - Opened by igrigorik over 7 years ago - 2 comments

#46 - Complete PR for testing beacon

Issue - State: closed - Opened by toddreifsteck over 7 years ago - 2 comments

#46 - Complete PR for testing beacon

Issue - State: closed - Opened by toddreifsteck over 7 years ago - 2 comments

#45 - Should cross-origin beacons with an ArrayBuffer payload do a CORS preflight?

Issue - State: closed - Opened by cdumez over 7 years ago - 3 comments

#44 - Update privacy & security section to reflect CORS processing logic.

Pull Request - State: closed - Opened by igrigorik almost 8 years ago - 4 comments

#43 - Privacy & Security section not current

Issue - State: closed - Opened by annevk almost 8 years ago - 1 comment
Labels: bug, security-tracker

#42 - maximum data size rules still seem ambiguous

Issue - State: closed - Opened by dbaron almost 8 years ago - 2 comments

#42 - maximum data size rules still seem ambiguous

Issue - State: closed - Opened by dbaron almost 8 years ago - 2 comments

#41 - Tests for CORS and sendBeacon()

Issue - State: closed - Opened by annevk about 8 years ago - 5 comments
Labels: test:missing-coverage

#40 - ArrayBuffer uses "application/octet-stream" as default Content-Type in impl

Issue - State: closed - Opened by annevk about 8 years ago - 19 comments
Labels: test:missing-coverage

#39 - Enforce payload limits via Fetch API

Pull Request - State: closed - Opened by igrigorik over 8 years ago - 11 comments

#38 - Ambiguity on "maximum data size" limit and enforcement

Issue - State: closed - Opened by igrigorik over 8 years ago - 18 comments

#37 - Beacon is only exposed to Worker in Microsoft Edge

Issue - State: closed - Opened by toddreifsteck over 8 years ago - 4 comments

#36 - Transition Level 1 to CR

Issue - State: closed - Opened by igrigorik over 8 years ago - 5 comments
Labels: w3c

#35 - Set the keep-alive flag in the fetch sendBeacon performs

Issue - State: closed - Opened by domenic over 8 years ago

#34 - switch to whitelist for corsMode

Pull Request - State: closed - Opened by igrigorik over 8 years ago - 33 comments

#33 - Set request's cors mode based on payload's object type

Pull Request - State: closed - Opened by igrigorik over 8 years ago - 7 comments

#32 - CO Redirect in the face of CORs may not be correct in specs

Issue - State: closed - Opened by toddreifsteck over 8 years ago - 10 comments

#31 - Privacy concern caused by unspecified delay of requests

Issue - State: closed - Opened by Rob--W almost 9 years ago - 9 comments

#30 - Allow setting HTTP(S) headers in beacon

Issue - State: closed - Opened by bhamiltoncx almost 9 years ago - 3 comments

#30 - Allow setting HTTP(S) headers in beacon

Issue - State: closed - Opened by bhamiltoncx almost 9 years ago - 3 comments

#29 - Need to add tests for sendBeacon

Issue - State: closed - Opened by toddreifsteck almost 9 years ago - 4 comments

#29 - Need to add tests for sendBeacon

Issue - State: closed - Opened by toddreifsteck almost 9 years ago - 4 comments

#28 - Fix a typo

Pull Request - State: closed - Opened by prayagverma about 9 years ago - 1 comment

#28 - Fix a typo

Pull Request - State: closed - Opened by prayagverma about 9 years ago - 1 comment

#27 - Add method to sendBeacon

Pull Request - State: closed - Opened by toddreifsteck about 9 years ago - 60 comments

#26 - Privacy + security cleanup

Pull Request - State: closed - Opened by igrigorik about 9 years ago - 5 comments

#25 - normativity of language in Privacy and Security section

Issue - State: closed - Opened by npdoty about 9 years ago - 1 comment

#24 - Without trailing slash you get http

Pull Request - State: closed - Opened by annevk about 9 years ago - 1 comment

#23 - Cleanup processing and security & privacy

Pull Request - State: closed - Opened by igrigorik about 9 years ago - 2 comments

#23 - Cleanup processing and security & privacy

Pull Request - State: closed - Opened by igrigorik about 9 years ago - 2 comments

#22 - Should sendBeacon support GET?

Issue - State: closed - Opened by toddreifsteck about 9 years ago - 14 comments

#21 - Is "ensuring" correct?

Issue - State: closed - Opened by npdoty about 9 years ago - 5 comments

#20 - Request coalescing as a platform primitive?

Issue - State: closed - Opened by igrigorik about 9 years ago - 14 comments

#19 - Clarify & simplify

Pull Request - State: closed - Opened by igrigorik about 9 years ago - 3 comments

#19 - Clarify & simplify

Pull Request - State: closed - Opened by igrigorik about 9 years ago - 3 comments

#18 - editorial comments

Issue - State: closed - Opened by plehegar over 9 years ago - 2 comments
Labels: enhancement, security-tracker

#17 - privacy considerations

Issue - State: closed - Opened by plehegar over 9 years ago - 13 comments
Labels: security-tracker

#16 - security considerations and CORS

Issue - State: closed - Opened by plehegar over 9 years ago - 1 comment
Labels: security-tracker

#15 - Skip body processing

Issue - State: closed - Opened by plehegar over 9 years ago - 13 comments
Labels: security-tracker

#14 - Privacy section is misguided

Issue - State: closed - Opened by annevk over 9 years ago - 8 comments
Labels: bug, security-tracker

#13 - Give guidelines on unload/visibilitystate/pagehide

Issue - State: closed - Opened by plehegar over 9 years ago - 1 comment

#13 - Give guidelines on unload/visibilitystate/pagehide

Issue - State: closed - Opened by plehegar over 9 years ago - 1 comment

#12 - Fix broken links

Issue - State: closed - Opened by igrigorik over 9 years ago - 1 comment

#11 - call Fetch to extract byte stream and content type

Pull Request - State: closed - Opened by igrigorik over 9 years ago - 3 comments

#10 - Clarify interaction with CORS (preflight requests)

Issue - State: closed - Opened by igrigorik over 9 years ago - 23 comments

#9 - Address Security/Privacy feedback from TPAC 2014

Issue - State: closed - Opened by plehegar almost 10 years ago - 9 comments

#9 - Address Security/Privacy feedback from TPAC 2014

Issue - State: closed - Opened by plehegar almost 10 years ago - 9 comments

#8 - Change the context for the beacon fetch to 'beacon'

Pull Request - State: closed - Opened by ehsan almost 10 years ago

#7 - The context for fetching the beacon should be "beacon"

Issue - State: closed - Opened by ehsan almost 10 years ago - 5 comments

#6 - Firefox and Accept /

Issue - State: closed - Opened by plehegar about 10 years ago - 4 comments
Labels: question

#5 - Beacon-Age registration

Issue - State: closed - Opened by plehegar over 10 years ago - 5 comments
Labels: enhancement

#4 - TAG comments?

Issue - State: closed - Opened by plehegar over 10 years ago - 1 comment

#3 - respec version of Beacon

Pull Request - State: closed - Opened by plehegar over 10 years ago - 6 comments

#2 - privacy and security considerations

Issue - State: closed - Opened by plehegar over 10 years ago - 3 comments
Labels: enhancement

GitHub / w3c/beacon issues and pull requests