Thanks for the clarification.
I think the idea (as you explained it) sounds great, hope you guys can get it
working. :)
From: jforres...@wikimedia.org
Date: Tue, 16 Dec 2014 22:06:11 -0800
To: wikitech-l@lists.wikimedia.org
Subject: Re: [Wikitech-l] [BREAKING CHANGE] Plans to move Cite
Ehm, has accessibility been taken into account with this design ? Quoting
WebAIM: Always use native HTML markup to provide the necessary semantic
content and meaning, then use CSS to enhance and change the default styles.
I can't fully tell from just looking that the patches.
DJ
On Wed, Dec 17,
On Wed, Dec 17, 2014 at 2:50 PM, Derk-Jan Hartman
d.j.hartman+wmf...@gmail.com wrote:
Ehm, has accessibility been taken into account with this design ? Quoting
WebAIM: Always use native HTML markup to provide the necessary semantic
content and meaning, then use CSS to enhance and change the
On Tue, Dec 16, 2014 at 9:10 PM, James Forrester jforres...@wikimedia.org
wrote:
On 16 December 2014 at 04:45, Brad Jorsch (Anomie) bjor...@wikimedia.org
wrote:
On Tue, Dec 16, 2014 at 5:44 AM, Marc Ordinas i Llopis
marc...@wikimedia.org wrote:
Due to how MediaWiki's messages system
I've written a simple MediaWiki extension that uses an instance of the
W3C Validator service (via the Services_W3C_HTMLValidator
http://pear.php.net/package/Services_W3C_HTMLValidator PEAR package)
to validate SVG images hosted on a wiki. It is meant to replace the
current system on Commons,
Can anyone think of a reason *not* to eliminate wgParser usage from
WikitextContent? I have a bug (T76651) that is resolved by making
WikitextContent use its own parser instance rather than wgParser. I wrote
an experimental fix of WikitextContent that clones the parser in the same
way as
Hi everyone
I'm pleased to (belatedly) welcome another new member of the Services team:
Marko Obrovac. Marko started working in the Services team with Gabriel
Wicke and James Douglas on RESTbase.
Marko comes to us from Reflected Networks, a Croatian web-hosting company
specializing in
On 17 December 2014 at 10:43, Rob Lanphier ro...@wikimedia.org wrote:
Hi everyone
I'm pleased to (belatedly) welcome another new member of the Services team:
Marko Obrovac. Marko started working in the Services team with Gabriel
Wicke and James Douglas on RESTbase.
Welcome!
J.
--
James
https://www.mediawiki.org/wiki/Scrum_of_scrums/2014-12-17
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hi, the RT migration to Phabricator is starting right now.
All the RT queues have been frozen. Please don't send any emails to @
rt.wikimedia.org. This includes access-requests@ and procurement@, the two
RT queues that will not be migrated at this point, which will be in
read-only mode during the
Hello everyone,
I would like to announce the release of MediaWiki 1.24.1, 1.23.8, 1.22.15 and
1.19.23. This is a regular security and maintenance release. Download links are
given at the end of this email. Please note this release marks the end of
lifetime for MediaWiki 1.22 branch.
==
Hello,
I found out we do not run on extensions the 'structure' testsuite of
mediawiki/core. It is made of three tests in tests/phpunit/structure
AutoLoaderTest.php verify classes are properly registered, and the
autloader entries point to an actual file
ResourcesTest.php ditto for the
On 18/12/14 03:40, Keith Welter wrote:
Can anyone think of a reason *not* to eliminate wgParser usage from
WikitextContent? I have a bug (T76651) that is resolved by making
WikitextContent use its own parser instance rather than wgParser. I wrote
an experimental fix of WikitextContent that
== Security fixes in 1.24.1, 1.23.8, 1.22.15 and 1.19.23 ==
* (bug T76686) [SECURITY] thumb.php outputs wikitext message as raw HTML,
which could lead to xss. Permission to edit MediaWiki namespace is
required
to exploit this.
Really? That's stretching the definition of a security bug.
On Thu, 18 Dec 2014 07:44:59 +0100, Brian Wolff bawo...@gmail.com wrote:
== Security fixes in 1.24.1, 1.23.8, 1.22.15 and 1.19.23 ==
* (bug T76686) [SECURITY] thumb.php outputs wikitext message as raw
HTML,
which could lead to xss. Permission to edit MediaWiki namespace is
required
to
15 matches
Mail list logo
