site dev help megathread

>webshit

Don't ping !codecels for that.

aren't divs supposed to work? https://devrama.net/post/131/me-on-the-right/102786#context

anyways u can use the scale property to frick up the page compeltely lol

also are u sure that you allowed it for spans? check this comment out https://devrama.net/post/131/me-on-the-right/102787#context

I would like my 5k mbux rn pls thx

https://devrama.net/@transb-word/wall/comment/102793#context

Are animations allowed, or just a single call?

what is the rdrama tech stack? I became a manager so I don't code enough anymore.

Rotated in the preview heh

I can't believe you're actually going to implement it you're the best

Can I get the badge?

How many times will schizo break the Code before we enact a final solution

>be schizocel

>decide to make a schizopost

>decide to add a ton of unnecessary formatting

>fuck up and forget a $$ somewhere

>realize it didn't do the needful

>edit the post and re-add the $$

>decide to complain to aevann without telling him about the edit

True story, happened four schizodays ago

See this post where I reproduced the bug. The $$ that was not included was the one before in @Sneaky's details tag.

<details><summary>@bballbelle</summary>
$$:marseywould:$$
</details>
<details><summary>@jararaca</summary>
$$:marseywould:$$
</details>
<details><summary>@salamander</summary>
$$:marseywould:$$
</details>
<details><summary>@tejanx</summary>
$$:marseywould:$$
</details>
<details><summary>@AmbyTheGoblin</summary>
$$:marseywould:$$
</details>
<details><summary>@eleganza</summary>
$$:marseywould:$$
</details>
<details><summary>@pillowprincess</summary>
$$:marseywould:$$
</details>
<details><summary>@sodajerk </summary>
$$:marseywould:$$
</details>
<details><summary>@dramasexual</summary>
$$:marseywould:$$
</details>
<details><summary>@maggotz</summary>
$$:marseywould:$$
</details>
<details><summary>@plsnope</summary>
$$:marseywould:$$
</details>
<details><summary>@moonbearer</summary>
$$:marseywould:$$
</details>
<details><summary>@kongwrwr</summary>
$$:marseywould:$$
</details>
<details><summary>@nancy-pelosi</summary>
$$:marseywould:$$
</details>
<details><summary>@isern-i-phail</summary>
$$:marseywould:$$
</details>
<details><summary>@swampwater</summary>
$$:marseywould:$$
</details>
<details><summary>@footfucker44</summary>
$$:marseywould:$$
</details>
<details><summary>@winterwonderland</summary>
$$:marseywould:$$
</details>
<details><summary>@groyperchilla</summary>
$$:marseywould:$$
</details>
<details><summary>@sneaky</summary>
:marseywould:$$
</details>
<details><summary>@lesbianbarbie</summary>
$$:marseywould:$$
</details>
<details><summary>@llamabean</summary>
$$:marseywould:$$
</details>
<details><summary>@enoby</summary>
$$:marseywould:$$
</details>
<details><summary>@gaydinosaurtrain</summary>
$$:marseywould:$$
</details>
<details><summary>@summerland</summary>
$$:marseywould:$$
</details>
<details><summary>@phedre</summary>
$$:marseywould:$$
</details>
<details><summary>@lilmarseyontheprairie</summary>
$$:marseywould:$$
</details>

SHOW MORE

why did this happen

Idk but I managed to reproduce it here and here by copying and pasting the options in edits. I don't know how to reproduce it consistently. Often when I copy and paste the options and save the edit, the $$'s remain as $$'s and don't turn into options. I think it's relevant that the options are the same (all ). It appears that it's taking the $$'s from two different places and treating the </details><details><summary></summary>'s in between as the poll options. Then it somehow breaks the HTML and causes parts of the post to go outside the post-text container.

Because it’s a double negative canceling the first click

Happens when the anthem was toggled on in the first place right? Maybe it's because you need user input to play media in the first place which is 1 click and in the code it's waiting for the media to play before it toggles it off using your 2nd click

I didn't look at the code and I'm pretty much talking out of my butt but that's my guess

There's probably a bug.

Remove this function, whoever added it is r-slurred: https://fsdfsd.net/rDrama/rDrama/src/commit/80824ade1252a5c378e11af8d5cb44a702d2a2b2/files/assets/js/profile_song.js#L73

You can tell this is the culprit because if you click anywhere on the page before clicking the button, it works correctly

I can't tell you exactly why it happens this way, but I'm inclined to say that the event handler attached to the button is evaluated first, pausing the music, and then the click event bubbles up to the document, where the handler sees that the audio is paused and invokes the play function.

Bugchasing megathread

Black women?

Don’t click it twice.

BUG FIXED MY NEIGHBOR

Open and close the report modal multiple times and check the event listeners—every time the modal is opened, an event listener on the submit button is re-added. You can either directly set the onclick property of the button to make sure that there is only one custom event listener (easy, but kinda awful), or you can remove the event listener every time the modal closes (better approach, use the same thing on line 8 in comments_v.js to get the instance and add the corresponding removeEventListener).

while(true){

catch(error){}}

There you go it should fix all you're bugs, @KongDong_of_Uganda is happy @KongDong_of_Uganda could be of help!

Trans lives matter

throttling submissions would probably be the best way of fixing this, would also prevent people from actually double clicking it. hmm looks like postToast only has a callback for success right? ideally you'd handle enabling it on any response, so i'd probably just patch this with a timer to prevent double submits - either with a variable like this or by disabling the button.

edit: oh didn't realize this was all on window, can probably chuck the canSubmit on reportCommentButton.canSubmit = true in that case

let canSubmit = true;
reportCommentButton.addEventListener('click', function() {
	if (!canSubmit) return;
	canSubmit = false;
	setTimeout( function() {
		canSubmit = true;
	}, 1000 );

	this.innerHTML='Reporting comment';

	postToast(this, `/report/comment/${id}`,
		{
			"reason": reason_comment.value
		},
		() => { canSubmit = true }
	);
})

posts.sub IS NULL

Don't do this for one.

You should explain exactly what you're trying to achieve with the query. There may be better approaches.

Probably not with adding a simple index.

I would add a new column for "rank", index that new column sorted ASC. Then have a job that runs every X minutes that computes and updates each post rank.

When querying, you can sort/limit by the pre-computed rank but then apply a live rank algo in real-time so that it's not stale from the job but would need some tweaks/optimizations to work around page boundaries accurately.

The ampersand (&) needs to be escaped in HTML because it's a special character used to introduce an HTML entity. Here's a brief breakdown:

1. HTML Entities: These are used to represent reserved characters in HTML that cannot be used as they are because they have special meanings. For instance, the less-than sign (<) starts a tag. To actually display a less-than sign, you'd use its entity, <.

2. Ampersand's Role: The ampersand itself is used to begin these entities. For example, < for <, > for >, and & for &.

3. Potential for Confusion: If you were to use an ampersand directly and followed it by characters that form a known entity, the browser might interpret it as an entity rather than as the intended text. For example, if you intended to write "M&M's" but wrote it as "M&Ms", a browser might interpret the "&Ms" as an entity (even if it's not a valid one).

4. Safety: By always escaping the ampersand as &, you ensure that the ampersand is always treated as a literal character and not the start of an entity. This reduces the risk of unexpected display issues or potential vulnerabilities.

In summary, the need to escape the ampersand in HTML arises from its role as the initiator of HTML entities. Escaping it ensures clarity and prevents unintended interpretations by the browser.

isn't it because & is a control character? It's used to display all characters which are otherwise reserved for internal use, <, > etc

because of html entities? &nbsp; and so on

>codescels up whole site

>doesn't know about escape characters

Because of all other escapes like & nbsp;

Because it has a special meaning. In urls, as a separator and html, as a reference I think.

Test: &&&

What the frick kind of unescaping code is this site using?

That video is blocked in canada (and presumably elsewhere). I don't get the error you do though.

works for me neighbor

windows 10 brave

Is Youtube banned in eygpt