mirror of
https://git.sr.ht/~seirdy/seirdy.one
synced 2024-11-10 00:12:09 +00:00
Use <aside> for reply context
Makes it play better with reading modes, etc
This commit is contained in:
parent
81ccde1d3b
commit
6b8dd5a657
2 changed files with 5 additions and 3 deletions
|
@ -305,7 +305,7 @@ picture > img {
|
|||
/* WCAG Technique C25: use borders to separate sections.
|
||||
* Also use "content-visibility: auto" to improve performance by
|
||||
* reducing the number of DOM nodes rendered at once. */
|
||||
aside,
|
||||
aside nav,
|
||||
footer,
|
||||
section[role="doc-endnotes"],
|
||||
section[aria-labelledby="webmentions"] {
|
||||
|
|
|
@ -2,9 +2,11 @@
|
|||
title: "Answer engines"
|
||||
date: 2022-05-25T19:59:08+00:00
|
||||
---
|
||||
<p role="note">
|
||||
<aside role="note">
|
||||
|
||||
Reply to {{< mention-work itemprop="about" itemtype="BlogPosting" reply=true >}}{{<cited-work name="Is DuckDuckGo, DuckDuckDone?" extraName="headline" url="https://kevq.uk/is-duckduckgo-duckduckdone/">}} by {{<indieweb-person first-name="Kev" last-name="Quirk" url="https://kevq.uk/about/" itemprop="author">}}{{</mention-work>}}
|
||||
</p>
|
||||
|
||||
</aside>
|
||||
|
||||
I read your article and share similar concerns. Using Microsoft Bing and Google Search's commercial APIs generally requires accepting some harsh terms, including a ban on mixing <abbr title="Search Engine Result Pages">SERPs</abbr> from multiple sources (this is why Ixquick shut down and the company pivoted to the Google-exclusive Startpage search service). But the requirement to allow trackers in a companion web browser was new to me.
|
||||
|
||||
|
|
Loading…
Reference in a new issue