Why is the current clue text constrained to 481px?

[DKMiller71]

I've been wondering: why does the current clue text seem to be constrained to 481px? On my page and other users' pages, it seems that the clue area is scrunched up (and wrapping) to fit over the grid instead of being allowed to use the horizontal area across the page (such as over the columns of clues) if the page is wider. Is there a reason for this?

I see that if I tinker with its width, it takes away the space of the columns of clues, so it might be the nesting order, but it had me wondering.

[viresh-ratnakar]

On phones, and in most cases in blogs (that carry the crossword in the main central column and other stuff on either side), only the grid-width is reliably visible. So I've opted to keep the code simple: the current-clue div is nested within the grid-panel. Iirc, at one point I had played around with changing this (indeed to use the full width when available), but was somehow not satisfied with what I got.

All that said, I will maybe give it another shot, as I do not remember exactly what I ran into.

Can you point me to some example puzzles/clues where you see the clue area as "scrunched up"? I looked at this one but it looked OK to me (Chrome/Linux).

[DKMiller71]

Like this, for example...

[DKMiller71]

Experimenting, I made the following changes in my local copy (attached, search on DKM):

Moved lines 584-589 (${this.prefix}-curr-clue and its children) up to below 579 (${this.prefix}-clear-area)

Changed line 5120:
this.currClue.style.width = '100%'; // widthPx;

This seemed to work, even if I changed the browser to mobile view or load the page into an iframe. But I don't know what other scenarios you might have in mind.
exolve-m.js.txt

[viresh-ratnakar]

Thanks, I'll take a look soon (it might take me a couple of days to get to this). - If I do do this (and chances are, I will, why not), I will add this as an *option* to opt into. I myself find the current layout quite acceptable (the word "scrunched" did not spring to my mind when I looked at the image that you attached :-)), but it's indeed possible that I'm just too used to it. - The other main thing I need to check is that this does not break Exet. Even if it does, I'm sure that's fixable, and I'll make any necessary tweaks to Exet as well.

…

On Tue, May 14, 2024 at 9:22 AM Darren Miller ***@***.***> wrote: Experimenting, I made the following changes (search on DKM) in <http://url> my local copy: Moved lines 584-589 (${this.prefix}-curr-clue and its children) up to below 579 (${this.prefix}-clear-area) Changed line 5120: this.currClue.style.width = '100%'; // widthPx; This seemed to work, even if I changed the browser to mobile view or load the page into an iframe. But I don't know what other scenarios you might have in mind. exolve-m.js.txt <https://github.com/viresh-ratnakar/exolve/files/15311321/exolve-m.js.txt> — Reply to this email directly, view it on GitHub <#101 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AJQ562FURVYXIN6M7N6RB23ZCI23PAVCNFSM6AAAAABHUSOA46VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TIMZWGA3DC> . You are receiving this because you commented.Message ID: ***@***.***>

[DKMiller71]

That's totally fine - whatever you think best. I have a workaround anyway....

inside customizeExolve(puz):

	puz.clearArea.after(puz.currClue);
	puz.resizeCurrClueAndControls = customResizeCurrClueAndControls;

Where customResizeCurrClueAndControls is just a copy of the original code with the replacement line:
this.currClue.style.width = '100%';