mirror of
https://github.com/hanzo-apps/hanzo.ai.git
synced 2026-10-29 07:20:43 +00:00
zeekay
e981114824
/chat signed out is the buying agent (components/sales/Guest, Agent): the
question the home composer carried in ?q= is asked of cloud's
POST /v1/ai/sales, the reply is drawn as text, and each next step the
server built is a control: a call (the lead is filed first, then the
calendar opens on it), the sign-up, a plan's card checkout, Add funds. A
quiet line says it is a limited preview and how many messages are left; at
the ceiling the sign-up takes the composer's place. A conversation's own
address still signs in, and a signed-in reader keeps the app.
/buying-specialist is the same agent; its keyword script, its typed prices
and its claims to see an account are gone. The model pages' no-key card is
the real lane, POST /v1/chat/public, not a guest key that answers 401.
Measured in the site's names: chat_started, cta_clicked {cta: kind, plan,
agent: sales}, sales_contacted. The floating privacy button is hidden as
room.css meant: the rule names its tag to outrank gui's atomic class.
21 lines
816 B
CSS
21 lines
816 B
CSS
/*
|
|
* @hanzo/ui's Consent draws a floating "Your Privacy Choices" button on any page
|
|
* that mounts no link of its own: in practice the app's pages, where it stood on
|
|
* the composer and on every pane. The choices are reached from the footer of
|
|
* every marketing page (ConsentLink), from Settings in the app, and from the bar
|
|
* the region's rule draws, so the floating button is never drawn. The element
|
|
* is named with its tag so the rule outranks gui's own atomic display class, which
|
|
* is one class like this attribute and is injected later.
|
|
*/
|
|
div[data-slot='consent-choices'] {
|
|
display: none;
|
|
}
|
|
|
|
/* The share card's topic chips scroll sideways on a phone with no scrollbar. */
|
|
[data-slot='beta-topic-row'] {
|
|
scrollbar-width: none;
|
|
}
|
|
[data-slot='beta-topic-row']::-webkit-scrollbar {
|
|
display: none;
|
|
}
|