Development Discussion Board

No, you got that wrong. Issue is latest post icon (red icon on left of topic title) is moved to its own line. Pagination is fine.

not actually an issue caused by anything in 3.2 it is there in 3.1 and is caused by horrible design/layout of prosilver so its not going to be a very clean fix, but ill look into it. No, its not in 3.1 and it is caused by changes in 3.2. More specifically by addition of display:inline-block to all ...

It is caused by using display:inline-block instead of display:inline on topic title: viewtopic.php?p=284116#p284116

Trimming is not a solution. Fixing display mode is.

However I'm still quite unsure how that would look like in practice (for example, what if the style uses different HTML then what the ext. author expects etc). In practice there are few issues I can think of: In phpBB templates are quite large, so searching for code might be more complex than neede...

Next thing you are going to ask how to make it work in Netscape 3? Nobody can help you with that because no sane person would waste time (first finding ancient computer with that browser, then banging head against the wall trying to make logical things work in ancient browser that doesn't understand...

It is caused by addition of this line: https://github.com/phpbb/phpbb/blob/master/phpBB/styles/prosilver/theme/links.css#L11 Browsers wrap inline and inline-block elements differently. When there are 2 inline elements in a row and whole text doesn't fit available width, browsers display split text l...

I think the main drawback of this would be that extensions could become incompatible with each other. Why? Replacing code doesn't mean old code is removed. So, for example, if some extension wants to append code after <!-- end of header -->, it should include search in replacement, allowing other e...

What do you mean by template modifications? See https://area51.phpbb.com/phpBB/viewtopic.php?t=43453&start=80 (second part of post and there is discussion on previous page of that thread) Its an idea implemented in vBulletin many years ago as third party add-on that quickly became very popular ...

Good point. With current template events system someone will get screwed - ether style devs or extension devs. Ideally whole system should be replaced with template modifications. It is way more powerful and flexible than template events and would make both style and extension developers happy. Howe...

I suggest to include template events to feature freeze for 3.2, so minor updates, like 3.2.1, wouldn't add new template events. Currently in 3.1 styles require updates for every minor release because of array of events that are added to templates. That means authors have to release updates every few...