zebra-spaces: relocate role-transition notice banner below 'your hand'
The role-change notices (you-are-now-a-speaker / stepped-down / moved- to-listener / promoted-to-cohost / now-the-host) sat above the room list — top-of-page real estate for what's actually a personal status update. Move sec-notice to sit BELOW sec-listener-actions so the message reads in the same gaze as the controls it affects.
This commit is contained in:
parent
6c93549685
commit
f1b7dc4330
1 changed files with 13 additions and 9 deletions
|
|
@ -707,13 +707,6 @@ try {
|
|||
</div>
|
||||
</section>
|
||||
|
||||
<section id="sec-notice" class="hidden">
|
||||
<div id="notice-banner" class="notice-banner warn">
|
||||
<span id="notice-text"></span>
|
||||
<button id="btn-notice-close" class="small">dismiss</button>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<section id="sec-room" class="hidden">
|
||||
<h2>room</h2>
|
||||
<div id="members"></div>
|
||||
|
|
@ -742,6 +735,17 @@ try {
|
|||
<p class="note" style="margin-top:0.4rem">you join muted so you don't interrupt the current conversation — tap "unmute" when you're ready to speak.</p>
|
||||
</section>
|
||||
|
||||
<!-- Role-transition notices (you are now a speaker / you were stepped
|
||||
down / you were moved to listener / etc.) live BELOW the 'your hand'
|
||||
section so the user reads them in the same gaze as the controls they
|
||||
affect — they're status updates about you, not page-level alerts. -->
|
||||
<section id="sec-notice" class="hidden">
|
||||
<div id="notice-banner" class="notice-banner warn">
|
||||
<span id="notice-text"></span>
|
||||
<button id="btn-notice-close" class="small">dismiss</button>
|
||||
</div>
|
||||
</section>
|
||||
|
||||
<section id="sec-latency" class="hidden">
|
||||
<h2>latency</h2>
|
||||
<div id="latency-rows" class="latency-rows"></div>
|
||||
|
|
@ -4122,8 +4126,8 @@ logLine('', 'ready — pick a handle, type a rendezvous code, enter the space');
|
|||
|
||||
<footer style="margin:2.2rem auto 0;font-size:0.65rem;color:#999;line-height:1.7;word-break:break-all;font-family:monospace">
|
||||
<span id="pi-seal" style="color:#777;cursor:default;user-select:none" title="">page integrity</span> · built <span class="stamp-date">2026-06-03</span><br>
|
||||
md5 <span class="stamp-md5">cf82551642844724ea70e85e58e54595</span><br>
|
||||
sha256 <span class="stamp-sha">c885d4cac28628f633bfd3b4cf7a0527e7b40a659ab478aa9fa4454bc0e6fabf</span><br>
|
||||
md5 <span class="stamp-md5">2ad425ad8790dc455a4b7deb8af3c46d</span><br>
|
||||
sha256 <span class="stamp-sha">391c031a7f92174ad58eed6fb15b0a091253655d52e09b87e6c0c1553888afc4</span><br>
|
||||
<span style="color:#bbb">hashes are of this page with these two fields zeroed — to verify, blank them and re-hash</span><br>
|
||||
<span style="color:#bbb">one self-contained file — <strong>save a copy</strong> and verify against these hashes; point at your own servers with ?signal= and ?turncred=, or <a href="host-your-own.html" style="color:#999">host your own community</a></span>
|
||||
</footer>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue