- Re: [whatwg/fetch] Fix: Appending a header to headers with "request-no-cors" guard (#840) Anne van Kesteren (Tuesday, 27 November)
- Re: [whatwg/fetch] Fix: Appending a header to headers with "request-no-cors" guard (#840) Anne van Kesteren (Tuesday, 27 November)
- Re: [whatwg/fetch] Fix: Appending a header to headers with "request-no-cors" guard (#840) Yutaka Hirano (Wednesday, 28 November)
- Re: [whatwg/fetch] Fix: Appending a header to headers with "request-no-cors" guard (#840) Yutaka Hirano (Wednesday, 28 November)
- Re: [whatwg/fetch] Fix: Appending a header to headers with "request-no-cors" guard (#840) Yutaka Hirano (Wednesday, 28 November)
- Re: [whatwg/fetch] Fix: Appending a header to headers with "request-no-cors" guard (#840) Yutaka Hirano (Wednesday, 28 November)
- Re: [whatwg/fetch] Fix: Appending a header to headers with "request-no-cors" guard (#840) Yutaka Hirano (Wednesday, 28 November)
- Re: [whatwg/fetch] Fix: Appending a header to headers with "request-no-cors" guard (#840) Yutaka Hirano (Wednesday, 28 November)
- Re: [whatwg/fetch] Fix: Appending a header to headers with "request-no-cors" guard (#840) Yutaka Hirano (Wednesday, 28 November)
- Re: [whatwg/fetch] Fix: Appending a header to headers with "request-no-cors" guard (#840) Anne van Kesteren (Wednesday, 28 November)
- Re: [whatwg/fetch] Fix: Appending a header to headers with "request-no-cors" guard (#840) Anne van Kesteren (Wednesday, 28 November)
- Re: [whatwg/fetch] Fix: Appending a header to headers with "request-no-cors" guard (#840) Yutaka Hirano (Thursday, 29 November)
- Re: [whatwg/streams] Add a brand check to pipeThrough() (#966) Domenic Denicola (Monday, 26 November)
- Re: [whatwg/streams] Add a brand check to pipeThrough() (#966) Domenic Denicola (Monday, 26 November)
- Re: [whatwg/streams] Add a brand check to pipeThrough() (#966) Mattias Buelens (Monday, 26 November)
- Re: [whatwg/streams] Add a brand check to pipeThrough() (#966) Adam Rice (Tuesday, 27 November)
- Re: [whatwg/streams] Add a brand check to pipeThrough() (#966) Adam Rice (Tuesday, 27 November)
- Re: [whatwg/streams] Add a brand check to pipeThrough() (#966) Adam Rice (Tuesday, 27 November)
- Re: [whatwg/streams] Add a brand check to pipeThrough() (#966) Mattias Buelens (Tuesday, 27 November)
- Re: [whatwg/streams] Add a brand check to pipeThrough() (#966) Domenic Denicola (Tuesday, 27 November)
- Re: [whatwg/streams] Add a brand check to pipeThrough() (#966) Adam Rice (Tuesday, 27 November)
- Re: [whatwg/streams] Add a brand check to pipeThrough() (#966) Adam Rice (Tuesday, 27 November)
- Re: [whatwg/streams] Constructor specification is unclear (#965) Adam Rice (Tuesday, 20 November)
- Re: [whatwg/streams] Constructor specification is unclear (#965) Jason Orendorff (Tuesday, 20 November)
- Re: [whatwg/streams] Constructor specification is unclear (#965) Domenic Denicola (Tuesday, 20 November)
- Re: [whatwg/streams] Constructor specification is unclear (#965) Adam Rice (Wednesday, 21 November)
- Re: [whatwg/streams] Constructor specification is unclear (#965) Domenic Denicola (Wednesday, 21 November)
- Re: [whatwg/streams] Constructor specification is unclear (#965) Adam Rice (Thursday, 22 November)
- Re: [whatwg/streams] Constructor specification is unclear (#965) Mattias Buelens (Thursday, 22 November)
- Re: [whatwg/streams] Constructor specification is unclear (#965) Adam Rice (Monday, 26 November)
- Re: [whatwg/streams] Constructor specification is unclear (#965) Mattias Buelens (Monday, 26 November)
- Re: [whatwg/streams] Constructor specification is unclear (#965) Adam Rice (Monday, 26 November)
- Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774) Anne van Kesteren (Tuesday, 20 November)
- Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774) freshp86 (Tuesday, 20 November)
- Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774) Anne van Kesteren (Wednesday, 21 November)
- Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774) Hugo (Wednesday, 21 November)
- Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774) Anne van Kesteren (Wednesday, 21 November)
- Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774) Hugo (Wednesday, 21 November)
- Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774) Anne van Kesteren (Wednesday, 21 November)
- Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774) freshp86 (Wednesday, 21 November)
- Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774) Hayato Ito (Thursday, 22 November)
- Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774) Caridy Patiño (Thursday, 22 November)
- Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774) freshp86 (Thursday, 22 November)
- Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774) Hugo (Thursday, 22 November)
- Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774) Anne van Kesteren (Thursday, 22 November)
- Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774) Caridy Patiño (Thursday, 22 November)
- Re: [w3c/webcomponents] tabIndex -1 behaves differently on non-Custom Elements (#774) Simon Taggart (Tuesday, 27 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcos Cáceres (Friday, 16 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcos Cáceres (Friday, 16 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcos Cáceres (Friday, 16 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Matt Giuca (Friday, 16 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcelo Volmaro (Friday, 16 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcos Cáceres (Sunday, 18 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcelo Volmaro (Sunday, 18 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcos Cáceres (Monday, 19 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcos Cáceres (Monday, 19 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcelo Volmaro (Monday, 19 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcos Cáceres (Monday, 19 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcos Cáceres (Monday, 19 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Matt Giuca (Monday, 19 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcos Cáceres (Monday, 19 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Matt Giuca (Monday, 19 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcos Cáceres (Monday, 19 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcos Cáceres (Monday, 19 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcos Cáceres (Monday, 19 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Matt Giuca (Monday, 19 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcos Cáceres (Monday, 19 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Matt Giuca (Monday, 26 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcelo Volmaro (Monday, 26 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Tobias Buschor (Monday, 26 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcos Cáceres (Wednesday, 28 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Matt Giuca (Wednesday, 28 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Kenneth Rohde Christiansen (Wednesday, 28 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcelo Volmaro (Wednesday, 28 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcos Cáceres (Wednesday, 28 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Alexey Rodionov (Wednesday, 28 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Matt Giuca (Wednesday, 28 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Robert Linder (Wednesday, 28 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Matt Giuca (Wednesday, 28 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Robert Linder (Wednesday, 28 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Matt Giuca (Thursday, 29 November)
- Re: [w3c/manifest] Add optional `translations` member (#676) Marcos Cáceres (Thursday, 29 November)
- Re: [w3c/manifest] Breaking: Ignore any icon with no recognised purpose. (#741) Kenneth Rohde Christiansen (Thursday, 15 November)
- Re: [w3c/manifest] Breaking: Ignore any icon with no recognised purpose. (#741) Matt Giuca (Thursday, 15 November)
- Re: [w3c/manifest] Breaking: Ignore any icon with no recognised purpose. (#741) Matt Giuca (Thursday, 15 November)
- Re: [w3c/manifest] Breaking: Ignore any icon with no recognised purpose. (#741) Marcos Cáceres (Friday, 16 November)
- Re: [w3c/manifest] Breaking: Ignore any icon with no recognised purpose. (#741) Matt Giuca (Friday, 16 November)
- Re: [w3c/manifest] Breaking: Ignore any icon with no recognised purpose. (#741) Matt Giuca (Friday, 16 November)
- Re: [w3c/manifest] Breaking: Ignore any icon with no recognised purpose. (#741) Marcos Cáceres (Friday, 16 November)
- Re: [w3c/manifest] Breaking: Ignore any icon with no recognised purpose. (#741) Marcos Cáceres (Friday, 16 November)
- Re: [w3c/manifest] Breaking: Ignore any icon with no recognised purpose. (#741) Matt Giuca (Friday, 16 November)
- Re: [w3c/manifest] Breaking: Ignore any icon with no recognised purpose. (#741) Matt Giuca (Friday, 16 November)
- Re: [w3c/manifest] Breaking: Ignore any icon with no recognised purpose. (#741) Matt Giuca (Friday, 16 November)
- Re: [w3c/manifest] Breaking: Ignore any icon with no recognised purpose. (#741) Matt Giuca (Friday, 16 November)
- Re: [w3c/manifest] Breaking: Ignore any icon with no recognised purpose. (#741) Matt Giuca (Friday, 16 November)
- Re: [w3c/manifest] Breaking: Ignore any icon with no recognised purpose. (#741) Marcos Cáceres (Friday, 16 November)
- Re: [w3c/manifest] Breaking: Ignore any icon with no recognised purpose. (#741) Marcos Cáceres (Friday, 16 November)
- Re: [w3c/manifest] Breaking: Ignore any icon with no recognised purpose. (#741) Marcos Cáceres (Friday, 16 November)
- Re: [w3c/manifest] Breaking: Ignore any icon with no recognised purpose. (#741) Marcos Cáceres (Friday, 16 November)
- Re: [w3c/webcomponents] mousedown on a light DOM element should be able to focus on a shadow container (#773) Ryosuke Niwa (Wednesday, 14 November)
- Re: [w3c/webcomponents] mousedown on a light DOM element should be able to focus on a shadow container (#773) Jan Miksovsky (Wednesday, 14 November)
- Re: [w3c/webcomponents] mousedown on a light DOM element should be able to focus on a shadow container (#773) Ryosuke Niwa (Wednesday, 14 November)
- Re: [w3c/webcomponents] mousedown on a light DOM element should be able to focus on a shadow container (#773) Hayato Ito (Thursday, 15 November)
- Re: [w3c/webcomponents] mousedown on a light DOM element should be able to focus on a shadow container (#773) Jan Miksovsky (Thursday, 15 November)
- Re: [w3c/webcomponents] mousedown on a light DOM element should be able to focus on a shadow container (#773) Jan Miksovsky (Thursday, 15 November)
- Re: [w3c/webcomponents] mousedown on a light DOM element should be able to focus on a shadow container (#773) Hayato Ito (Friday, 16 November)
- Re: [w3c/webcomponents] mousedown on a light DOM element should be able to focus on a shadow container (#773) Hayato Ito (Friday, 16 November)
- Re: [w3c/webcomponents] mousedown on a light DOM element should be able to focus on a shadow container (#773) Ryosuke Niwa (Friday, 16 November)
- Re: [w3c/webcomponents] mousedown on a light DOM element should be able to focus on a shadow container (#773) Ryosuke Niwa (Friday, 16 November)
- Re: [w3c/webcomponents] mousedown on a light DOM element should be able to focus on a shadow container (#773) Hayato Ito (Friday, 16 November)
- Re: [w3c/webcomponents] mousedown on a light DOM element should be able to focus on a shadow container (#773) Hayato Ito (Friday, 16 November)
- Re: [w3c/webcomponents] mousedown on a light DOM element should be able to focus on a shadow container (#773) Ryosuke Niwa (Friday, 16 November)
- Re: [w3c/manifest] Respec validator (#740) Marcos Cáceres (Wednesday, 14 November)
- Re: [w3c/manifest] Respec validator (#740) Marcos Cáceres (Wednesday, 14 November)
- Re: [w3c/manifest] Respec validator (#740) Marcos Cáceres (Wednesday, 14 November)
- Re: [w3c/manifest] Respec validator (#740) Marcos Cáceres (Wednesday, 14 November)
- Re: [w3c/manifest] Respec validator (#740) Marcos Cáceres (Wednesday, 14 November)
- Re: [w3c/manifest] Respec validator (#740) Kenneth Rohde Christiansen (Wednesday, 14 November)
- Re: [w3c/manifest] Respec validator (#740) Marcos Cáceres (Wednesday, 14 November)
- Re: [w3c/manifest] Respec validator (#740) Marcos Cáceres (Wednesday, 14 November)
- Re: [w3c/manifest] Respec validator (#740) Marcos Cáceres (Thursday, 15 November)
- Re: [w3c/manifest] Respec validator (#740) Marcos Cáceres (Thursday, 15 November)
- Re: [w3c/manifest] Respec validator (#740) Marcos Cáceres (Thursday, 15 November)
- Re: [w3c/manifest] Respec validator (#740) Marcos Cáceres (Thursday, 15 November)
- Re: [w3c/manifest] Respec validator (#740) Marcos Cáceres (Thursday, 15 November)
- Re: [w3c/manifest] Respec validator (#740) Marcos Cáceres (Thursday, 15 November)
- Re: [w3c/manifest] Respec validator (#740) Marcos Cáceres (Thursday, 15 November)
- Re: [w3c/manifest] Respec validator (#740) Marcos Cáceres (Friday, 16 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Anne van Kesteren (Wednesday, 14 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Ryosuke Niwa (Wednesday, 14 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Ryosuke Niwa (Wednesday, 14 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) jgraham (Thursday, 15 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Caridy Patiño (Thursday, 15 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) jgraham (Thursday, 15 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Ryosuke Niwa (Thursday, 15 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) jgraham (Thursday, 15 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Ryosuke Niwa (Thursday, 15 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Lars den Bakker (Friday, 16 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Anne van Kesteren (Friday, 16 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Hayato Ito (Friday, 16 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Emilio Cobos Álvarez (Friday, 16 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Lars den Bakker (Friday, 16 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Diego Ferreiro Val (Monday, 19 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Geoffrey Sneddon (Monday, 19 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) jgraham (Monday, 19 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Caridy Patiño (Monday, 19 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) David Burns (Monday, 19 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Lars den Bakker (Monday, 19 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Caridy Patiño (Monday, 19 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Lars den Bakker (Monday, 19 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Ryosuke Niwa (Monday, 19 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Caridy Patiño (Monday, 19 November)
- Re: [w3c/webcomponents] [WebDriver] Testability of web components (#771) Ryosuke Niwa (Monday, 19 November)
- Re: [w3c/editing] CFC: Move ExecCommand to WICG (#185) chaals (Tuesday, 13 November)
- Re: [w3c/editing] CFC: Move ExecCommand to WICG (#185) Johannes Wilm (Tuesday, 13 November)
- Re: [w3c/editing] CFC: Move ExecCommand to WICG (#185) Léonie Watson (Tuesday, 13 November)
- Re: [w3c/editing] CFC: Move ExecCommand to WICG (#185) Johannes Wilm (Tuesday, 13 November)
- Re: [w3c/editing] CFC: Move ExecCommand to WICG (#185) Florian Rivoal (Wednesday, 14 November)
- Re: [w3c/editing] CFC: Move ExecCommand to WICG (#185) Florian Rivoal (Wednesday, 14 November)
- Re: [w3c/editing] CFC: Move ExecCommand to WICG (#185) Marcos Cáceres (Wednesday, 14 November)
- Re: [w3c/editing] CFC: Move ExecCommand to WICG (#185) Johannes Wilm (Wednesday, 14 November)
- Re: [w3c/editing] CFC: Move ExecCommand to WICG (#185) Florian Rivoal (Wednesday, 14 November)
- Re: [w3c/editing] CFC: Move ExecCommand to WICG (#185) Marcos Cáceres (Wednesday, 14 November)
- Re: [w3c/editing] CFC: Move ExecCommand to WICG (#185) Léonie Watson (Wednesday, 14 November)
- Re: [w3c/editing] CFC: Move ExecCommand to WICG (#185) Marcos Cáceres (Wednesday, 14 November)
- Re: [w3c/editing] CFC: Move ExecCommand to WICG (#185) Johannes Wilm (Wednesday, 14 November)
- Re: [w3c/editing] CFC: Move ExecCommand to WICG (#185) Marcos Cáceres (Wednesday, 14 November)
- Re: [w3c/editing] CFC: Move ExecCommand to WICG (#185) Léonie Watson (Thursday, 22 November)
- Re: [w3c/editing] CFC: Move ExecCommand to WICG (#185) Léonie Watson (Thursday, 22 November)
- Re: [w3c/manifest] chore(.travis): check spec for errors/warnings (#739) Marcos Cáceres (Tuesday, 13 November)
- Re: [w3c/manifest] chore(.travis): check spec for errors/warnings (#739) Marcos Cáceres (Tuesday, 13 November)
- Re: [w3c/manifest] chore(.travis): check spec for errors/warnings (#739) Marcos Cáceres (Tuesday, 13 November)
- Re: [w3c/manifest] chore(.travis): check spec for errors/warnings (#739) Marcos Cáceres (Tuesday, 13 November)
- Re: [w3c/manifest] chore(.travis): check spec for errors/warnings (#739) Marcos Cáceres (Tuesday, 13 November)
- Re: [w3c/manifest] chore(.travis): check spec for errors/warnings (#739) Matt Giuca (Tuesday, 13 November)
- Re: [w3c/manifest] chore(.travis): check spec for errors/warnings (#739) Marcos Cáceres (Tuesday, 13 November)
- Re: [w3c/manifest] chore(.travis): check spec for errors/warnings (#739) Marcos Cáceres (Tuesday, 13 November)
- Re: [w3c/manifest] chore(.travis): check spec for errors/warnings (#739) Marcos Cáceres (Tuesday, 13 November)
- Re: [w3c/manifest] chore(.travis): check spec for errors/warnings (#739) Marcos Cáceres (Tuesday, 13 November)
- Re: [w3c/manifest] chore(.travis): check spec for errors/warnings (#739) Matt Giuca (Tuesday, 13 November)
- Re: [w3c/manifest] chore(.travis): check spec for errors/warnings (#739) Marcos Cáceres (Tuesday, 13 November)
- Re: [whatwg/storage] Proposal: Add detailed usage breakdown in estimate() (#63) Anne van Kesteren (Tuesday, 13 November)
- Re: [whatwg/storage] Proposal: Add detailed usage breakdown in estimate() (#63) Andrew Sutherland (Tuesday, 13 November)
- Re: [whatwg/storage] Proposal: Add detailed usage breakdown in estimate() (#63) Domenic Denicola (Tuesday, 13 November)
- Re: [whatwg/storage] Proposal: Add detailed usage breakdown in estimate() (#63) aliams (Wednesday, 14 November)
- Re: [whatwg/storage] Proposal: Add detailed usage breakdown in estimate() (#63) ralphch0 (Wednesday, 14 November)
- Re: [whatwg/storage] Proposal: Add detailed usage breakdown in estimate() (#63) Jarryd (Wednesday, 14 November)
- Re: [whatwg/storage] Proposal: Add detailed usage breakdown in estimate() (#63) Andrew Sutherland (Wednesday, 14 November)
- Re: [whatwg/storage] Proposal: Add detailed usage breakdown in estimate() (#63) Jarryd (Friday, 16 November)
- Re: [whatwg/storage] Proposal: Add detailed usage breakdown in estimate() (#63) Andrew Sutherland (Friday, 16 November)
- Re: [whatwg/storage] Proposal: Add detailed usage breakdown in estimate() (#63) Joshua Bell (Friday, 16 November)
- Re: [whatwg/storage] Proposal: Add detailed usage breakdown in estimate() (#63) Jarryd (Tuesday, 27 November)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) Henri Sivonen (Monday, 12 November)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) Anne van Kesteren (Monday, 12 November)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) Henri Sivonen (Tuesday, 13 November)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) Henri Sivonen (Monday, 19 November)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) Henri Sivonen (Monday, 19 November)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) Dr. Ken Lunde (Wednesday, 21 November)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) Dr. Ken Lunde (Wednesday, 21 November)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) Dr. Ken Lunde (Wednesday, 21 November)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) Henri Sivonen (Thursday, 22 November)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) EarlgreyTea (Friday, 23 November)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) Dr. Ken Lunde (Friday, 23 November)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) EarlgreyTea (Friday, 23 November)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) Dr. Ken Lunde (Friday, 23 November)
- Re: [whatwg/encoding] Concatenating two ISO-2022-JP outputs from a conforming encoder doesn't result in conforming input (#115) EarlgreyTea (Friday, 23 November)
- Re: [whatwg/fetch] Define the response Content-Type header parser (#831) Anne van Kesteren (Friday, 9 November)
- Re: [whatwg/fetch] Define the response Content-Type header parser (#831) Anne van Kesteren (Monday, 12 November)
- Re: [whatwg/fetch] Define the response Content-Type header parser (#831) Anne van Kesteren (Monday, 12 November)
- Re: [whatwg/fetch] Define the response Content-Type header parser (#831) Anne van Kesteren (Monday, 12 November)
- Re: [whatwg/fetch] Define the response Content-Type header parser (#831) Anne van Kesteren (Monday, 12 November)
- Re: [whatwg/fetch] Define the response Content-Type header parser (#831) Anne van Kesteren (Monday, 12 November)
- Re: [whatwg/fetch] Define the response Content-Type header parser (#831) Anne van Kesteren (Monday, 12 November)
- Re: [whatwg/fetch] Define the response Content-Type header parser (#831) Anne van Kesteren (Monday, 12 November)
- Re: [whatwg/fetch] Define the response Content-Type header parser (#831) Anne van Kesteren (Monday, 12 November)
- Re: [whatwg/fetch] Define the response Content-Type header parser (#831) Domenic Denicola (Monday, 12 November)
- Re: [whatwg/fetch] Define the response Content-Type header parser (#831) Domenic Denicola (Monday, 12 November)
- Re: [whatwg/fetch] Define the response Content-Type header parser (#831) Anne van Kesteren (Tuesday, 13 November)
- Re: [whatwg/fetch] Define the response Content-Type header parser (#831) Anne van Kesteren (Tuesday, 13 November)
- Re: [whatwg/fetch] Define the response Content-Type header parser (#831) Anne van Kesteren (Tuesday, 13 November)
- Re: [whatwg/fetch] Define the response Content-Type header parser (#831) Anne van Kesteren (Tuesday, 13 November)
- Re: [whatwg/fetch] Define the response Content-Type header parser (#831) Anne van Kesteren (Tuesday, 13 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Tuesday, 13 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Tuesday, 13 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Tuesday, 13 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Matt Menke (Tuesday, 13 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Tuesday, 13 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Tuesday, 13 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Boris Zbarsky (Tuesday, 13 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Wednesday, 14 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Wednesday, 14 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Wednesday, 14 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Thursday, 15 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Matt Menke (Friday, 16 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Monday, 19 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Monday, 19 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Monday, 19 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Monday, 19 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Matt Menke (Monday, 19 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Matt Menke (Monday, 19 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Tuesday, 20 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Matt Menke (Tuesday, 20 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Domenic Denicola (Tuesday, 20 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Domenic Denicola (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Domenic Denicola (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Domenic Denicola (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Domenic Denicola (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Matt Menke (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Matt Menke (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Matt Menke (Wednesday, 21 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Domenic Denicola (Thursday, 22 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Thursday, 22 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Thursday, 22 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Thursday, 22 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Matt Menke (Monday, 26 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Tuesday, 27 November)
- Re: [whatwg/fetch] Define the Content-Type header parser (#831) Anne van Kesteren (Tuesday, 27 November)
- Re: [w3c/manifest] Editorial: fix some xrefs (#734) Marcos Cáceres (Thursday, 8 November)
- Re: [w3c/manifest] Editorial: fix some xrefs (#734) Matt Giuca (Thursday, 8 November)
- Re: [w3c/manifest] Editorial: fix some xrefs (#734) Marcos Cáceres (Thursday, 8 November)
- Re: [w3c/manifest] Editorial: fix some xrefs (#734) Matt Giuca (Thursday, 8 November)
- Re: [w3c/manifest] Editorial: fix some xrefs (#734) Matt Giuca (Thursday, 8 November)
- Re: [w3c/manifest] Editorial: fix some xrefs (#734) Marcos Cáceres (Thursday, 8 November)
- Re: [w3c/manifest] Editorial: fix some xrefs (#734) Marcos Cáceres (Thursday, 8 November)
- Re: [w3c/manifest] Editorial: fix some xrefs (#734) Marcos Cáceres (Thursday, 8 November)
- Re: [w3c/manifest] Editorial: fix some xrefs (#734) Marcos Cáceres (Thursday, 8 November)
- Re: [w3c/manifest] Editorial: fix some xrefs (#734) Marcos Cáceres (Thursday, 8 November)
- Re: [whatwg/streams] Switching to Web IDL (#963) Adam Rice (Thursday, 8 November)
- Re: [whatwg/streams] Switching to Web IDL (#963) Michael[tm] Smith (Friday, 9 November)
- Re: [whatwg/streams] Switching to Web IDL (#963) Chris Mills (Friday, 9 November)
- Re: [whatwg/streams] Switching to Web IDL (#963) youennf (Friday, 9 November)
- Re: [whatwg/streams] Switching to Web IDL (#963) Till Schneidereit (Friday, 16 November)
- Re: [whatwg/streams] Switching to Web IDL (#963) Ms2ger (Friday, 16 November)
- Re: [whatwg/streams] Switching to Web IDL (#963) Till Schneidereit (Friday, 16 November)
- Re: [whatwg/streams] Switching to Web IDL (#963) Adam Rice (Tuesday, 20 November)
- Re: [whatwg/streams] Switching to Web IDL (#963) Anne van Kesteren (Tuesday, 20 November)
- Re: [whatwg/streams] Switching to Web IDL (#963) Domenic Denicola (Wednesday, 21 November)
- Re: [whatwg/streams] Switching to Web IDL (#963) Adam Rice (Wednesday, 21 November)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280) Yves Lafon (Friday, 9 November)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280) Mike West (Friday, 9 November)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280) Daniel Appelquist (Tuesday, 13 November)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280) Mike West (Tuesday, 13 November)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280) Mark Nottingham (Tuesday, 13 November)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280) Mike West (Wednesday, 14 November)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280) Mark Nottingham (Wednesday, 14 November)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280) Mike West (Thursday, 15 November)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280) Lukasz Olejnik (Sunday, 18 November)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280) arturjanc (Sunday, 18 November)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280) Mark Nottingham (Sunday, 18 November)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280) arturjanc (Monday, 19 November)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280) Mark Nottingham (Monday, 19 November)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280) Anne van Kesteren (Monday, 19 November)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280) Devdatta Akhawe (Thursday, 22 November)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280) Daniel Appelquist (Wednesday, 28 November)
- Re: [w3ctag/design-reviews] `sec-metadata` (#280) Daniel Appelquist (Wednesday, 28 November)
- Re: [w3c/manifest] Autopublish failing (#729) Matt Giuca (Wednesday, 7 November)
- Re: [w3c/manifest] Autopublish failing (#729) Marcos Cáceres (Wednesday, 7 November)
- Re: [w3c/manifest] Autopublish failing (#729) Matt Giuca (Wednesday, 7 November)
- Re: [w3c/manifest] Autopublish failing (#729) Matt Giuca (Wednesday, 7 November)
- Re: [w3c/manifest] Autopublish failing (#729) Matt Giuca (Wednesday, 7 November)
- Re: [w3c/manifest] Autopublish failing (#729) Matt Giuca (Wednesday, 7 November)
- Re: [w3c/manifest] Autopublish failing (#729) Marcos Cáceres (Wednesday, 7 November)
- Re: [w3c/manifest] Autopublish failing (#729) Marcos Cáceres (Wednesday, 7 November)
- Re: [w3c/manifest] Autopublish failing (#729) Matt Giuca (Wednesday, 7 November)
- Re: [w3c/manifest] Autopublish failing (#729) Marcos Cáceres (Thursday, 8 November)
- Re: [w3ctag/design-reviews] Wide gamut support for Canvas/OffscreenCanvas/ImageBitmap (#315) Anne van Kesteren (Wednesday, 7 November)
- Re: [w3ctag/design-reviews] Wide gamut support for Canvas/OffscreenCanvas/ImageBitmap (#315) Fernando Serboncini (Friday, 9 November)
- Re: [w3ctag/design-reviews] Wide gamut support for Canvas/OffscreenCanvas/ImageBitmap (#315) L. David Baron (Monday, 26 November)
- Re: [w3ctag/design-reviews] Wide gamut support for Canvas/OffscreenCanvas/ImageBitmap (#315) Chris Lilley (Thursday, 29 November)
- Re: [w3ctag/design-reviews] Wide gamut support for Canvas/OffscreenCanvas/ImageBitmap (#315) Chris Lilley (Thursday, 29 November)
- Re: [w3ctag/design-reviews] Wide gamut support for Canvas/OffscreenCanvas/ImageBitmap (#315) Fernando Serboncini (Thursday, 29 November)
- Re: [w3ctag/design-reviews] Wide gamut support for Canvas/OffscreenCanvas/ImageBitmap (#315) Fernando Serboncini (Thursday, 29 November)
- Re: [w3ctag/design-reviews] Wide gamut support for Canvas/OffscreenCanvas/ImageBitmap (#315) ccameron-chromium (Thursday, 29 November)
- Re: [w3ctag/design-reviews] Wide gamut support for Canvas/OffscreenCanvas/ImageBitmap (#315) Chris Lilley (Thursday, 29 November)
- Re: [w3ctag/design-reviews] Wide gamut support for Canvas/OffscreenCanvas/ImageBitmap (#315) Chris Lilley (Thursday, 29 November)
- Re: [w3ctag/design-reviews] Wide gamut support for Canvas/OffscreenCanvas/ImageBitmap (#315) ccameron-chromium (Thursday, 29 November)
- Re: [w3ctag/design-reviews] Wide gamut support for Canvas/OffscreenCanvas/ImageBitmap (#315) Chris Lilley (Friday, 30 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Daniel Ehrenberg (Friday, 2 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Domenic Denicola (Wednesday, 7 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Caridy Patiño (Wednesday, 7 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Daniel Ehrenberg (Wednesday, 7 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Ryosuke Niwa (Thursday, 8 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Anne van Kesteren (Thursday, 8 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Ryosuke Niwa (Thursday, 8 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Daniel Ehrenberg (Thursday, 8 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Domenic Denicola (Thursday, 8 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Anne van Kesteren (Thursday, 8 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Domenic Denicola (Thursday, 8 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Domenic Denicola (Thursday, 8 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Caridy Patiño (Thursday, 8 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Ryosuke Niwa (Friday, 9 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Anne van Kesteren (Friday, 9 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Domenic Denicola (Friday, 9 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) TAMURA, Kent (Thursday, 15 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Ryosuke Niwa (Thursday, 15 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Anne van Kesteren (Thursday, 15 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Ryosuke Niwa (Thursday, 15 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) TAMURA, Kent (Friday, 16 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Joe Pea (Monday, 19 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) TAMURA, Kent (Monday, 19 November)
- Re: [w3c/webcomponents] How to define APIs only for custom element authors (#758) Domenic Denicola (Monday, 19 November)
- Re: [w3ctag/design-reviews] HTTP State Tokens (#297) Mike West (Thursday, 1 November)
- Re: [w3ctag/design-reviews] HTTP State Tokens (#297) michael-oneill (Thursday, 1 November)
- Re: [w3ctag/design-reviews] HTTP State Tokens (#297) Mike West (Monday, 5 November)
- Re: [w3ctag/design-reviews] HTTP State Tokens (#297) michael-oneill (Tuesday, 6 November)
- Re: [w3ctag/design-reviews] HTTP State Tokens (#297) Mike West (Tuesday, 6 November)
- Re: [w3ctag/design-reviews] HTTP State Tokens (#297) Hadley Beeman (Wednesday, 28 November)
- Re: [w3ctag/design-reviews] HTTP State Tokens (#297) Hadley Beeman (Wednesday, 28 November)
- Re: [w3ctag/design-reviews] HTTP State Tokens (#297) L. David Baron (Wednesday, 28 November)
- Re: [w3ctag/design-reviews] HTTP State Tokens (#297) Lukasz Olejnik (Wednesday, 28 November)
- Re: [w3ctag/design-reviews] HTTP State Tokens (#297) michael-oneill (Wednesday, 28 November)
- Re: [w3c/editing] Move execCommand to WICG (#184) chaals (Thursday, 1 November)
- Re: [w3c/editing] Move execCommand to WICG (#184) Johannes Wilm (Sunday, 11 November)
- Re: [w3c/editing] Move execCommand to WICG (#184) Marcos Cáceres (Monday, 12 November)
- Re: [w3c/editing] Move execCommand to WICG (#184) Marcos Cáceres (Monday, 12 November)
- Re: [w3c/editing] Move execCommand to WICG (#184) Johannes Wilm (Monday, 12 November)
- Re: [w3c/editing] Move execCommand to WICG (#184) Marcos Cáceres (Monday, 12 November)
- Re: [w3c/editing] Move execCommand to WICG (#184) Johannes Wilm (Monday, 12 November)
- Re: [w3c/editing] Move execCommand to WICG (#184) Chris Wilson (Tuesday, 13 November)
- Re: [w3c/editing] Move execCommand to WICG (#184) Johannes Wilm (Tuesday, 13 November)
- Re: [w3c/editing] Move execCommand to WICG (#184) Ryosuke Niwa (Tuesday, 13 November)
- Re: [w3c/editing] Move execCommand to WICG (#184) Marcos Cáceres (Tuesday, 13 November)
- Re: [w3c/editing] Move execCommand to WICG (#184) Johannes Wilm (Tuesday, 13 November)
- Re: [w3c/editing] Move execCommand to WICG (#184) Marcos Cáceres (Tuesday, 13 November)
- Re: [w3c/editing] Move execCommand to WICG (#184) Johannes Wilm (Wednesday, 14 November)
- Re: [w3c/editing] Move execCommand to WICG (#184) Marcos Cáceres (Wednesday, 14 November)
- Re: [w3c/editing] Move execCommand to WICG (#184) Marcos Cáceres (Wednesday, 14 November)
- Re: [w3c/editing] Move execCommand to WICG (#184) Marcos Cáceres (Wednesday, 14 November)
Last message date: Friday, 30 November 2018 22:59:58 UTC