VE doesn't use the debug log at all, it seems. This adds a single
wfDebugLog call so that the person using the debug log can see that it
actually does hit VE.
Also, returns better information for parsoid errors.
For example, without it, a parsoid misconfiguration of setInterwiki()
gives:
Error loading data from server: parsoidserver-http-bad-status:
500. Would you like to retry?
with it, you get something like the following:
Error loading data from server: parsoidserver-http-bad-status:
500: Page Fetch failure for "BADURL": Error: getaddrinfo
ENOTFOUND. Would you like to retry?
or
Error loading data from server: parsoidserver-http-bad-status:
500: Page Fetch failure for "BADURL": 404. Would you like to
retry?
Bug: 39057
Bug: 43147
Bug: 63149
Change-Id: I52db9fac42d7c0228b93ce3caec470fff98254f0
New changes:
d635974 Use staging instead of undo in annotation inspector
29233b8 Localisation updates from https://translatewiki.net.
efb3296 Localisation updates from https://translatewiki.net.
cfc5ad1 Localisation updates from https://translatewiki.net.
c609e02 Update OOjs to v1.1.0
dd2398c Update OOjs UI to v0.1.0-pre (adfcf92c6a)
Change-Id: Id122cd8a266554fdbe9f10dcdf53d87c7dd21b17
That function needs to return the result immediately, not wait for module loading (via mw.notify).
This was breaking us being able to keep track of what wikitextWarning object was in use (but only
the first time we used the module), and therefore fail to close the warning when the wikitext
disappeared.
Bug: 70168
Change-Id: I0f1427423a5fe82ec8e70e2f0462a3044ca7ace8
New changes:
378bc4c Polyfill Node.prototype.normalize in IE
d54cd30 Call onTargetInputChange when the link inspector is ready
00f7a00 Only undo if an initial annotation was applied
5d39686 Make filibuster code debug only
fdda60a Track selectionBefore in staging transactions
Change-Id: I2a70d599838b3575c5b0a63ffc60d023b04a8e80
There are still bugs and we're not marking it as a supported
browser yet, but it's no longer unusable.
Bug: 50085
Change-Id: I86b152da4c5dd895335d6f76b91c44f2eb3cd1a4
IE doesn't accept null as a "do nothing" value, only undefined.
If you return null, it'll show a popup with the text "null".
Change-Id: I984a7ded483c4c178cbca2a9af9abd895e6ded56
New changes:
7a2e989 Update OOjs UI to v0.1.0-pre (43f379c884)
Local changes:
Eliminate all references to Agora, now Minerva
Change-Id: I497e122a35090a909b1fbb00d0a9487d97e09da1
New changes:
235faf9 Try a bit harder not to create empty text nodes
72f9aff Followup 355be3ed: fix getOffset() behavior inside block aliens
c81dd57 Trigger handleDelete inside onCut
edb4c60 Only block language change if dir hasn't changed
15cce1d Localisation updates from https://translatewiki.net.
Change-Id: Ic205fd2ae9ddc3f870b74a49bfc02fea9a14546a
Make sure the image model can switch parameters when the image
source is switched, rather than having to instantiate a new
image model.
Also, when the image is changed, retain aspect ratio but make sure
to preserve the width of the previous image (unless the new image
is smaller)
Added 'resizeToBoundingBox' and 'scaleToThumbnailSize' static methods
in MWImageNode that return scaled dimensions based on the image
dimensions and the bounding box detals.
Depends on core change Idbb8b29db8e
Bug: 69450
Bug: 68000
Change-Id: I4327c86a9127f46da5522dc1197411fda757d5a4
New changes:
8592238 Localisation updates from https://translatewiki.net.
446b53d Remove unnecessary execCommand('undo') from onCut
Change-Id: I804eb7dbb0205780bdae06db45cc9c94f09eab02
* Toolbar was too tall
** The actions toolbar is nested in the main toolbar, so the rule
increasing the font size by 25% for toolbars applied to it twice
* Font size in link suggestions was too big
** Remove 25% font size increase from overlays
** Add it back on the context (otherwise it's too small)
** But only on the main surface's context (otherwise contexts in dialogs are too big)
* Make highlights and context appear below, not above, toolbar menus
** z-index: 4 was too high for the overlay, because MenuToolGroup also has 4
** But the default of z-index: 1 is too low because it puts dialogs behind the surface
** z-index: 2 seems to work
Bug: 69949
Change-Id: I19da270abcdbe526ff213f0eb7d0859b48276930
New changes:
e06966f Fix the newline bunny-hop bug harder
bb7afae dm.NodeFactory: Use .lookup() instead of .create().constructor
d18a33f Localisation updates from https://translatewiki.net.
fce9ad2 Check for selection in ve.ce.Surface#onDocumentFocus
Change-Id: I3dd706d956c409418c761a95cc631575fb36b8e9
If you got an edit conflict, the save dialog would
dead-end: there was no way for you to actually get to
the edit conflict resolution page because we were
hiding the resolve button.
Bug: 69150
Change-Id: Iaccb7d0ec25d8f15398e437d614184433c33e6eb
New changes:
c66e7a8 Update oo#compare usages
bbff57b Followup 8c71904: use getter for availableTools
f9587e8 Add myself to AUTHORS.txt
ffc9358 Localisation updates from https://translatewiki.net.
1025f3b Fix JS error in ce.LanguageAnnotation when dir is set but lang isn't
4ad483f Check IME simulations actually fail as expected
aaa991a Followup bbff57b, 8c71904: use getter for availableTools, again
Change-Id: I5bfa1201f38f2b86234535ed97a1c394d9cf8e58
The categories table holds all categories that exist OR have at one
point existed. This means it also contains a lot of vandalism and
other inappropriate names that happily come up in the suggestions.
This is undesirable. This changes the query to only list categories
with at least 1 entry.
Though technically it can be argued that an empty category with an
existing page might 'exist' and should thus be listed, with this
change they won't be. I don't think that is terribly incorrect to
say that such would be a 'new category', but we could also consider
renaming the label in the suggestion list to say:
'Currently unused category' or something similar.
As far as I can tell there is no way to test for page existance OR
generate a list based on allcategories with one API query.
Bug: 70025
Change-Id: I0e195d3ce26e69d4710d6a505b9da7d1b7678d92
