Development Discussion Board

My point is that as far as I know, we only use jQuery to toggle classes and select elements. Not super sure about this, so I might be wrong, however, basically all the browsers we want to support should support JS features that would make it simple to do this (e.g. they have querySelector etc). Vue ...

I would vote for droping jQuery, and using pure JS instead (basically jQuery shouldn't really have anything anymore that is harder to do in pure JS). For the more complicated stuff we could use Vue if there is a need for it.

However: It may be , that DSGVO suggests or forces us to have the cookies as "opt in" . As you guys have cookie consent from Insites implemented, and they have also an opt-in option: Is it planned to implement this function? And, of course, if the user is not accepting cookies, to block a...

I don't see this to be a good idea for phpBB. phpMyAdmin is whole project dedicated to do just that and only for MySQL. This would be just too much of a hassle to maintain, and honestly I don't really see this being widely used as you describe it. IMO most admins would just use it as a replacement o...

pell is not an editor, calling it a library would still be a huge overstatement.

Derk's username is Derky, and I'm Máté. You can find all usernames here . The mentor allocation for projects may change, as we plan to have at least two mentors for each project, and also one mentor shouldn't have too many students, so in general it is best to keep all conversations public, unless y...

Keep in mind, that you're free to propose any implementation (as you are also free to propose your own idea as well). Thus everything you read here is more of a suggestion than a requirement.

It depends which git client you use, the search term i would suggest is "Squash commits". I use the command line, so if you issue git commands from your console, then you want to rebase with the -i switch, and then just write an f for your second commit, and it will be merged into the firs...

It failed because your merge commit doesn't follow the commit message format.

I'm not quite sure based on the topic you linked what feature set would qualify as a solution to this problem, so I'm not sure if the following answers any of your questions. That said, I think the best we could do is removing all the inline JS and CSS (which we should do anyway). From that point on...