Web Fonts Working Group - Activity in 2023

Past meetings

• 1 meeting.

  • 5 December 2023

    WebFonts WG Zoom call, 5 December 2023.

GitHub

w3c/ift-encoder

• 1 pull request opened.

  • 6 December 2023

    Add support for VF design space augmentation w3c/ift-encoder#81, by @garretrieger.

• 1 pull request merged.

  • 6 December 2023

    Add support for VF design space augmentation w3c/ift-encoder#81.

Past meetings

• 1 meeting.

  • 14 November 2023

    WebFonts WG Zoom call, 14 November 2023.

Participants

• 1 participant left.

  • 1 November 2023

    Myles Maxfield (Apple Inc.) left.

GitHub

w3c/ift-encoder

• 5 pull requests opened.

  • 30 November 2023

    Some minor refactoring. w3c/ift-encoder#80, by @garretrieger.

  • 27 November 2023

    Add support for augmenting by features. w3c/ift-encoder#79, by @garretrieger.

  • 20 November 2023

    Update encoder to ensure loca length stays the same in mixed mode. w3c/ift-encoder#78, by @garretrieger.

  • 17 November 2023

    Add unique ptr's for hb_face/font/blob_t and fix memory leaks found in tests. w3c/ift-encoder#77, by @garretrieger.

  • 16 November 2023

    Implement support for mixed shared brotli and IFTB patches in the same font. w3c/ift-encoder#76, by @garretrieger.

• 5 pull requests merged.

  • 30 November 2023

    Some minor refactoring. w3c/ift-encoder#80.

  • 27 November 2023

    Add support for augmenting by features. w3c/ift-encoder#79.

  • 20 November 2023

    Update encoder to ensure loca length stays the same in mixed mode. w3c/ift-encoder#78.

  • 17 November 2023

    Add unique ptr's for hb_face/font/blob_t and fix memory leaks found in tests. w3c/ift-encoder#77.

  • 16 November 2023

    Implement support for mixed shared brotli and IFTB patches in the same font. w3c/ift-encoder#76.

w3c/woff

• 1 pull request merged.

  • 29 November 2023

    Feature/Add Python 3 compatibility to WOFF validator w3c/woff#7.

• 1 pull request received 4 new comments.

  • Latest comment 29 November 2023

    Feature/Add Python 3 compatibility to WOFF validator w3c/woff#7 (4 comments by @garretrieger, @w3cbot)

w3c/IFT

• 1 pull request opened.

  • 24 November 2023

    Update references to RFC9110, RFC9111 and RFC9112 w3c/IFT#154, by @tidoust.

• 1 pull request merged.

  • 27 November 2023

    Update references to RFC9110, RFC9111 and RFC9112 w3c/IFT#154.

• 1 pull request received 1 new comment.

  • 24 November 2023

    Update references to RFC9110, RFC9111 and RFC9112 w3c/IFT#154 (1 comment by @tidoust)

w3c/PFE-analysis

• 1 pull request closed.

  • 26 November 2023

    Add validation to merge tool. w3c/PFE-analysis#97.

Past meetings

• 1 meeting.

  • 24 October 2023

    WebFonts WG Zoom call, 24 October 2023.

GitHub

w3c/ift-encoder

• 2 pull requests opened.

  • 23 October 2023

    Demo updates w3c/ift-encoder#75, by @garretrieger.

  • 12 October 2023

    Add code for testing out static IFT. w3c/ift-encoder#74, by @garretrieger.

• 2 pull requests merged.

  • 23 October 2023

    Demo updates w3c/ift-encoder#75.

  • 16 October 2023

    Add code for testing out static IFT. w3c/ift-encoder#74.

w3c/woff

• 3 issues opened.

  • 9 October 2023

    Bit array not defined w3c/woff#30, by @Lorp.

  • 9 October 2023

    Distinguish "Decoding of bounding boxes" section from "Decoding of Composite Glyphs" section w3c/woff#29, by @Lorp.

  • 9 October 2023

    Clarify WOFF2 header majorVersion and minorVersion w3c/woff#28, by @Lorp.

• 1 issue closed.

  • 16 October 2023

    Bit array not defined w3c/woff#30.

• 1 issue received 1 new comment.

  • 16 October 2023

    Bit array not defined w3c/woff#30 (1 comment by @Lorp)

Past meetings

• 3 meetings.

  • 26 September 2023

    WebFonts WG Zoom call, 26 September 2023.

  • 12 September 2023

    WebFonts WG Zoom call, 12 September 2023.

  • 12 September 2023

    Web Fonts WG, 12 September 2023.

GitHub

w3c/IFT

• 9 issues closed.

  • 12 September 2023

    Range requests and preflights w3c/IFT#34.

  • 12 September 2023

    Supporting fonts with composite glyphs via range-request w3c/IFT#58.

  • 12 September 2023

    Using WOFF2 files with range-request mechanism doesn't seem to be a viable option w3c/IFT#59.

  • 12 September 2023

    Static file compression compatibility with range-request method w3c/IFT#60.

  • 12 September 2023

    Populate suggested character ordering for range-request method w3c/IFT#61.

  • 12 September 2023

    Update range-request document to use same fetch language that patch subset document uses w3c/IFT#67.

  • 12 September 2023

    Specifying Range Request implementation details w3c/IFT#79.

  • 12 September 2023

    Closing the initial range request connection, or leaving it open, may cause performance problems w3c/IFT#74.

  • 12 September 2023

    Advice on optimal arrangement for range requests? w3c/IFT#110.

• 10 issues received 10 new comments.

  • 26 September 2023

    Poor cacheing properties w3c/IFT#119 (1 comment by @garretrieger)

  • 12 September 2023

    Range requests and preflights w3c/IFT#34 (1 comment by @garretrieger)

  • 12 September 2023

    Supporting fonts with composite glyphs via range-request w3c/IFT#58 (1 comment by @garretrieger)

  • 12 September 2023

    Using WOFF2 files with range-request mechanism doesn't seem to be a viable option w3c/IFT#59 (1 comment by @garretrieger)

  • 12 September 2023

    Static file compression compatibility with range-request method w3c/IFT#60 (1 comment by @garretrieger)

  • 12 September 2023

    Populate suggested character ordering for range-request method w3c/IFT#61 (1 comment by @garretrieger)

  • 12 September 2023

    Update range-request document to use same fetch language that patch subset document uses w3c/IFT#67 (1 comment by @garretrieger)

  • 12 September 2023

    Specifying Range Request implementation details w3c/IFT#79 (1 comment by @garretrieger)

  • 12 September 2023

    Closing the initial range request connection, or leaving it open, may cause performance problems w3c/IFT#74 (1 comment by @garretrieger)

  • 12 September 2023

    Advice on optimal arrangement for range requests? w3c/IFT#110 (1 comment by @garretrieger)
• 1 pull request merged.

  • 7 September 2023

    Revamp the FeatureTagSet encoding scheme. w3c/IFT#149.

• 2 pull requests received 34 new comments.

  • Latest comment 7 September 2023

    IFTB draft w3c/IFT#151 (32 comments by @garretrieger, @skef)

  • Latest comment 7 September 2023

    Revamp the FeatureTagSet encoding scheme. w3c/IFT#149 (2 comments by @garretrieger, @vlevantovsky)

Past meetings

• 1 meeting.

  • 15 August 2023

    WebFonts WG Zoom call, 15 August 2023.

GitHub

w3c/IFT

• 1 issue opened.

  • 25 August 2023

    Compremised w3c/IFT#152, by @Dangerfield77.

• 1 issue closed.

  • 25 August 2023

    Compremised w3c/IFT#152.

• 1 issue received 7 new comments.

  • Latest comment 29 August 2023

    Poor cacheing properties w3c/IFT#119 (7 comments by @garretrieger, @martinthomson, @mnot)
• 2 pull requests opened.

  • 25 August 2023

    Update client and server handling to use "compression dictionary transport" headers w3c/IFT#153, by @garretrieger.

  • 22 August 2023

    IFTB draft w3c/IFT#151, by @skef.

• 1 pull request merged.

  • 29 August 2023

    Update client and server handling to use "compression dictionary transport" headers w3c/IFT#153.

• 3 pull requests received 3 new comments.

  • 27 August 2023

    Update client and server handling to use "compression dictionary transport" headers w3c/IFT#153 (1 comment by @svgeesus)

  • 22 August 2023

    IFTB draft w3c/IFT#151 (1 comment by @svgeesus)

  • 8 August 2023

    Revamp the FeatureTagSet encoding scheme. w3c/IFT#149 (1 comment by @garretrieger)

w3c/ift-encoder

• 1 pull request opened.

  • 9 August 2023

    Add a utility to extract and print client state (IFTP) from a font file. w3c/ift-encoder#73, by @garretrieger.

• 1 pull request merged.

  • 9 August 2023

    Add a utility to extract and print client state (IFTP) from a font file. w3c/ift-encoder#73.

Past meetings

• 2 meetings.

  • 25 July 2023

    WebFonts WG Zoom call, 25 July 2023.

  • 11 July 2023

    WebFonts WG Zoom call, 11 July 2023.

GitHub

w3c/ift-encoder

• 4 pull requests opened.

  • 21 July 2023

    Add util to convert base64 requests into human readable. w3c/ift-encoder#72, by @garretrieger.

  • 18 July 2023

    Add a public method to the client that can create the request from client state only. w3c/ift-encoder#71, by @garretrieger.

  • 11 July 2023

    Pass through identity encoded responses. w3c/ift-encoder#70, by @garretrieger.

  • 10 July 2023

    Use 'sbr' instead of 'brdiff' for content encoding. w3c/ift-encoder#69, by @garretrieger.

• 4 pull requests merged.

  • 21 July 2023

    Add util to convert base64 requests into human readable. w3c/ift-encoder#72.

  • 18 July 2023

    Add a public method to the client that can create the request from client state only. w3c/ift-encoder#71.

  • 11 July 2023

    Pass through identity encoded responses. w3c/ift-encoder#70.

  • 10 July 2023

    Use 'sbr' instead of 'brdiff' for content encoding. w3c/ift-encoder#69.

w3c/IFT

• 1 issue closed.

  • 13 July 2023

    Proposal would allow pages to learn how the user is interacting with the site w3c/IFT#50.

• 1 issue received 5 new comments.

  • Latest comment 13 July 2023

    Proposal would allow pages to learn how the user is interacting with the site w3c/IFT#50 (5 comments by @garretrieger, @svgeesus)
• 1 pull request opened.

  • 5 July 2023

    Use unicode Unified_Ideograph property to identify codepoints which require obfuscation. w3c/IFT#150, by @garretrieger.

• 1 pull request merged.

  • 13 July 2023

    Use unicode Unified_Ideograph property to identify codepoints which require obfuscation. w3c/IFT#150.

• 1 pull request received 5 new comments.

  • Latest comment 21 July 2023

    Revamp the FeatureTagSet encoding scheme. w3c/IFT#149 (5 comments by @garretrieger, @svgeesus)

Past meetings

• 2 meetings.

  • 20 June 2023

    WebFonts WG Zoom call, 20 June 2023.

  • 6 June 2023

    WebFonts WG Zoom call, 6 June 2023.

Participants

• 1 organization left.

  • 14 June 2023

    Loongson Technology Corporation Limited left.

GitHub

w3c/IFT

• 1 issue closed.

  • 19 June 2023

    Repeat fingerprinting analysis assuming a malicious font server w3c/IFT#42.

• 1 issue received 8 new comments.

  • Latest comment 29 June 2023

    Proposal would allow pages to learn how the user is interacting with the site w3c/IFT#50 (8 comments by @garretrieger, @pes10k, @svgeesus)
• 4 pull requests opened.

  • 20 June 2023

    Revamp the FeatureTagSet encoding scheme. w3c/IFT#149, by @garretrieger.

  • 16 June 2023

    Add codepoint obfuscation via grouping to the patch subset specification. w3c/IFT#148, by @garretrieger.

  • 15 June 2023

    Recommend using unicode-range in incremental @font-face's w3c/IFT#147, by @garretrieger.

  • 15 June 2023

    Add a mechanism to client state that prevents re-requesting codepoints w3c/IFT#146, by @garretrieger.

• 3 pull requests merged.

  • 19 June 2023

    Add codepoint obfuscation via grouping to the patch subset specification. w3c/IFT#148.

  • 19 June 2023

    Add a mechanism to client state that prevents re-requesting codepoints w3c/IFT#146.

  • 19 June 2023

    Recommend using unicode-range in incremental @font-face's w3c/IFT#147.

• 2 pull requests received 8 new comments.

  • Latest comment 28 June 2023

    Revamp the FeatureTagSet encoding scheme. w3c/IFT#149 (7 comments by @garretrieger, @skef, @svgeesus, @vlevantovsky)

  • 20 June 2023

    Add a mechanism to client state that prevents re-requesting codepoints w3c/IFT#146 (1 comment by @skef)

w3c/woff

• 1 issue closed.

  • 19 June 2023

    Typo: "wass" w3c/woff#24.

• 1 pull request opened.

  • 7 June 2023

    Fix typo. w3c/woff#27, by @garretrieger.

• 1 pull request merged.

  • 19 June 2023

    Fix typo. w3c/woff#27.

• 1 pull request received 2 new comments.

  • Latest comment 23 June 2023

    Fix typo in ReadUIntBase128 pseudo-code. w3c/woff#3 (2 comments by @w3cbot)

w3c/PFE-analysis

• 1 pull request opened.

  • 10 June 2023

    Update noise simulation report with updated findings on using codepoint grouping as a source of noise. w3c/PFE-analysis#103, by @garretrieger.

• 1 pull request merged.

  • 10 June 2023

    Update noise simulation report with updated findings on using codepoint grouping as a source of noise. w3c/PFE-analysis#103.

TR publications

• 2 documents published.

  • 30 May 2023

    Incremental Font Transfer published as a Working Draft. History of Incremental Font Transfer

  • 30 May 2023

    Range Request Incremental Font Transfer published as a Working Draft. History of Range Request Incremental Font Transfer

Past meetings

• 1 meeting.

  • 16 May 2023

    WebFonts WG Zoom call, 16 May 2023.

Participants

• 1 participant joined.

  • 15 May 2023

    Bianca Berning (W3C Invited Experts) joined.

GitHub

w3c/IFT

• 1 issue closed.

  • 16 May 2023

    Create an explainer for the IFT Patch Subset specification. w3c/IFT#124.

• 2 issues reopened.

  • 31 May 2023

    Poor cacheing properties w3c/IFT#119, by @garretrieger.

  • 25 May 2023

    Shared Brotli ID is expired w3c/IFT#101, by @svgeesus.

• 6 issues received 12 new comments.

  • Latest comment 25 May 2023

    Repeat fingerprinting analysis assuming a malicious font server w3c/IFT#42 (4 comments by @garretrieger, @svgeesus)

  • Latest comment 15 May 2023

    Create an explainer for the IFT Patch Subset specification. w3c/IFT#124 (4 comments by @garretrieger, @svgeesus, @vlevantovsky)

  • 31 May 2023

    Poor cacheing properties w3c/IFT#119 (1 comment by @garretrieger)

  • 26 May 2023

    Early wide review of IFT w3c/IFT#33 (1 comment by @svgeesus)

  • 25 May 2023

    Proposal would allow pages to learn how the user is interacting with the site w3c/IFT#50 (1 comment by @garretrieger)

  • 25 May 2023

    Shared Brotli ID is expired w3c/IFT#101 (1 comment by @svgeesus)
• 1 pull request opened.

  • 26 May 2023

    Changes for /TR publication w3c/IFT#145, by @svgeesus.

• 1 pull request merged.

  • 26 May 2023

    Changes for /TR publication w3c/IFT#145.

w3c/PFE-analysis

• 1 pull request opened.

  • 25 May 2023

    Add privacy simulation results. w3c/PFE-analysis#102, by @garretrieger.

• 1 pull request merged.

  • 25 May 2023

    Add privacy simulation results. w3c/PFE-analysis#102.

Past meetings

• 1 meeting.

  • 25 April 2023

    WebFonts WG Zoom call, 25 April 2023.

GitHub

w3c/ift-encoder

• 4 pull requests opened.

  • 26 April 2023

    Add additional set method for fontdata that allows both face and blob… w3c/ift-encoder#68, by @garretrieger.

  • 26 April 2023

    Add virtual destructor to ServerConfig. w3c/ift-encoder#67, by @garretrieger.

  • 26 April 2023

    All the font provider to be swapped out in server creation. w3c/ift-encoder#66, by @garretrieger.

  • 25 April 2023

    Add the option for FontData to store a face. w3c/ift-encoder#65, by @garretrieger.

• 4 pull requests merged.

  • 26 April 2023

    Add additional set method for fontdata that allows both face and blob… w3c/ift-encoder#68.

  • 26 April 2023

    Add virtual destructor to ServerConfig. w3c/ift-encoder#67.

  • 26 April 2023

    All the font provider to be swapped out in server creation. w3c/ift-encoder#66.

  • 26 April 2023

    Add the option for FontData to store a face. w3c/ift-encoder#65.

w3c/IFT

• 1 issue closed.

  • 24 April 2023

    Can't generate html w3c/IFT#143.

• 1 issue received 3 new comments.

  • Latest comment 12 April 2023

    Can't generate html w3c/IFT#143 (3 comments by @garretrieger, @tidoust)
• 1 pull request opened.

  • 12 April 2023

    Update rfc9110 and rfc9111 to use section references. w3c/IFT#144, by @garretrieger.

• 1 pull request merged.

  • 20 April 2023

    Update rfc9110 and rfc9111 to use section references. w3c/IFT#144.

Lifecycle

• 1 charter started.

  • 29 March 2023

    Chartered until 20 March 2025. Participants had to rejoin under this charter.

    Call for Participation

Past meetings

• 1 meeting.

  • 21 March 2023

    WebFonts WG Zoom call, 21 March 2023. Minutes.

GitHub

w3c/IFT

• 3 issues opened.

  • 21 March 2023

    Can't generate html w3c/IFT#143, by @skef.

  • 16 March 2023

    Condisderation w3c/IFT#140, by @svgeesus.

  • 16 March 2023

    Privacy Considerations says checksum is for error correction w3c/IFT#139, by @svgeesus.

• 6 issues closed.

  • 21 March 2023

    Consider placing client state as a table in the font. w3c/IFT#123.

  • 20 March 2023

    Privacy Considerations says checksum is for error correction w3c/IFT#139.

  • 17 March 2023

    Condisderation w3c/IFT#140.

  • 9 March 2023

    Novel, NIH things w3c/IFT#116.

  • 8 March 2023

    Security self-review answers for IFT w3c/IFT#35.

  • 8 March 2023

    I18n checklist answers for IFT w3c/IFT#36.

• 10 issues received 27 new comments.

  • Latest comment 12 March 2023

    Early wide review of IFT w3c/IFT#33 (7 comments by @garretrieger, @svgeesus)

  • Latest comment 24 March 2023

    Poor cacheing properties w3c/IFT#119 (4 comments by @garretrieger, @mnot)

  • Latest comment 9 March 2023

    Novel, NIH things w3c/IFT#116 (4 comments by @martinthomson, @svgeesus)

  • Latest comment 9 March 2023

    Repeat fingerprinting analysis assuming a malicious font server w3c/IFT#42 (3 comments by @npdoty, @svgeesus)

  • Latest comment 21 March 2023

    Can't generate html w3c/IFT#143 (2 comments by @garretrieger, @skef)

  • Latest comment 16 March 2023

    Create an explainer for the IFT Patch Subset specification. w3c/IFT#124 (2 comments by @svgeesus)

  • Latest comment 9 March 2023

    Supporting fonts with composite glyphs via range-request w3c/IFT#58 (2 comments by @svgeesus, @vlevantovsky)

  • 21 March 2023

    Consider placing client state as a table in the font. w3c/IFT#123 (1 comment by @garretrieger)

  • 17 March 2023

    Condisderation w3c/IFT#140 (1 comment by @svgeesus)

  • 8 March 2023

    Proposal would allow pages to learn how the user is interacting with the site w3c/IFT#50 (1 comment by @svgeesus)
• 3 pull requests opened.

  • 17 March 2023

    Update privacy section on checksums. w3c/IFT#142, by @garretrieger.

  • 17 March 2023

    fix typo, fixes #140 w3c/IFT#141, by @svgeesus.

  • 10 March 2023

    Split off the range request section back into a separate document. w3c/IFT#138, by @garretrieger.

• 5 pull requests merged.

  • 20 March 2023

    Update privacy section on checksums. w3c/IFT#142.

  • 17 March 2023

    fix typo, fixes #140 w3c/IFT#141.

  • 15 March 2023

    Split off the range request section back into a separate document. w3c/IFT#138.

  • 13 March 2023

    Remove PatchResponse from the specification w3c/IFT#137.

  • 1 March 2023

    Make client state part of the font file. w3c/IFT#136.

• 3 pull requests received 13 new comments.

  • Latest comment 15 March 2023

    Split off the range request section back into a separate document. w3c/IFT#138 (9 comments by @garretrieger, @skef, @svgeesus, @vlevantovsky)

  • Latest comment 8 March 2023

    Remove PatchResponse from the specification w3c/IFT#137 (3 comments by @garretrieger, @svgeesus)

  • 1 March 2023

    Make client state part of the font file. w3c/IFT#136 (1 comment by @garretrieger)

w3c/ift-encoder

• 1 pull request merged.

  • 3 March 2023

    Update client and server implementation to not use a client state font table and no PatchResponse w3c/ift-encoder#64.

Past meetings

• 1 meeting.

  • 21 February 2023

    WebFonts WG Zoom call, 21 February 2023.

Participants

• 1 participant left.

  • 21 February 2023

    Bram Stein (Adobe) left.

GitHub

w3c/ift-encoder

• 2 pull requests opened.

  • 28 February 2023

    Update client and server implementation to not use a client state font table and no PatchResponse w3c/ift-encoder#64, by @garretrieger.

  • 16 February 2023

    Migrate from custom StatusCode to absl::Status. w3c/ift-encoder#63, by @garretrieger.

• 1 pull request merged.

  • 16 February 2023

    Migrate from custom StatusCode to absl::Status. w3c/ift-encoder#63.

w3c/IFT

• 1 pull request opened.

  • 17 February 2023

    Remove PatchResponse from the specification w3c/IFT#137, by @garretrieger.

• 1 pull request received 4 new comments.

  • Latest comment 27 February 2023

    Make client state part of the font file. w3c/IFT#136 (4 comments by @svgeesus, @vlevantovsky)

Past meetings

• 1 meeting.

  • 24 January 2023

    WebFonts WG Zoom call, 24 January 2023.

GitHub

w3c/IFT

• 1 pull request opened.

  • 21 January 2023

    Make client state part of the font file. w3c/IFT#136, by @garretrieger.

w3c/ift-encoder

• 3 pull requests opened.

  • 11 January 2023

    Update harfbuzz to latest version. w3c/ift-encoder#62, by @garretrieger.

  • 11 January 2023

    Update to the latest emscripten w3c/ift-encoder#61, by @garretrieger.

  • 11 January 2023

    Check cbor return values in tests. w3c/ift-encoder#60, by @garretrieger.

• 3 pull requests merged.

  • 12 January 2023

    Update harfbuzz to latest version. w3c/ift-encoder#62.

  • 11 January 2023

    Update to the latest emscripten w3c/ift-encoder#61.

  • 11 January 2023

    Check cbor return values in tests. w3c/ift-encoder#60.

• 1 pull request received 1 new comment.

  • 11 January 2023

    Check cbor return values in tests. w3c/ift-encoder#60 (1 comment by @garretrieger)