Development Discussion Board

Well, doing something similar ATM... Was more like wondering why the unidiff format is not used instead of the context ones. Not really sure how many people end up patching files manually, however the current format sucks for that purpose and for readability as well.

No, it does not change anything functionality-wise.

bantu wrote:It was a revert, so we also reverted the whitespace changes. There is no point in just leaving whitespace changes in the 3.0.9-to-3.0.10 diff.

OK, thanks

Could someone please spend a couple of minutes explaining why the patchsets are not using unified diff format either by default, or why there is not an option to download the updates in that format? There are good reason why unidiff is a de-facto requirement when submitting patches to many open-sour...

Are all those whitespace changes in editor.js really intentional (most of them reverting the RC2 ones AFAICT and being rather inconsistent with the rest of the code) or a result of someone producing a couple-lines of patch in a differently set editor?

Sure thing, will do ASAP.

Really cannot believe this still has not been fixed. Open: styles/prosilver/theme/common.css Find: img { border-width: 0; } Replace with: img { border-width: 0; max-width: 100%; } This is extremely annoying when people post screenshots, the issue can be seen in loads of thread on the forum here.