Project:VisualEditor testing/Test

Hello, and welcome to the VisualEditor demonstration page. Do not expect edits here to stay for long; this page is like the sandbox.

'''Feedback here will likely be ignored. Please use VisualEditor/Feedback instead. Read VisualEditor/Welcome for the answers to many of your questions.'''

Note: The "VisualEditor" button only works with the Vector or MonoBook skins; see notes.

There are also specific test pages for templates, for references, and for formulæ.

= Heading 1a - Testing =

This is some text. This text has a bold and an italic word in it.

Heading 1b
The quick brown fox jumped over the lazy dog.

History tables always involve some concept of auditing, that is, keeping track of user actions. This means we need to protect against deliberate falsification of the history tables, which leads to two rules. First, a user must have no ability to directly DELETE rows from the history table, or they could erase the record of changes. Second, the user must have no ability to directly INSERT or UPDATE existing rows, because if they could they can falsify the history. These rules apply to both regular users and system administrators, the administrator must have no privelege to subvert or manipulate the history."Since history tables have a tendency to become seriously bloated, there must be some priveleged group that can DELETE from the history tables, which they would do as a periodic purge operation. This group should have no ability to UPDATE the tables, because such priveleges would open a potential hole for subverting the history. Regular system administrators should not be in this group, this should be a special group whose only purpose is to DELETE out of the history tables."If you are making use of DELTA columns, then stricly speaking you do not want to purge, but compress history tables. If you want to purge out all entries in 2005, you must replace them with a single entry that contains a SUM of the DELTA columns for all of 2005.

So to sum up, we have the following security rules for a history table:
 * No system user should be able to DELETE from the history table.
 * No system user should be able to UPDATE the history table.
 * No system user should be able to directly control the INSERT into the history table.
 * A special group must be defined whose only ability is to DELETE from the history table, so that the tables can be purged (or compressed) from time to time.

= Heading 2a - Testing =

Heading 3abc
= Heading 1b =

Heading 2bc
= Heading 3c = List item:
 * Foo

List item with formatted content:
 * Fooo

List item with a paragraph in it:
 * Baaaaar Baz

List item with multiple paragraphs in it:
 * First


 * Second


 * Third

List item with an internal link:
 * Baz

List item with an internal renamed, formatted link:
 * hhjhjk
 * kjlkjl


 * A Link Named Quux

List item with an external named link:
 * xkcd

List item with an external auto-numbered link:
 * 

Sequential list items and an empty list item with a paragraph following: Foo Bar Baz!
 * Last list item
 * No really, this is the last one
 * No, I really mean it this time.

Numbered list item:
 * 1) Foo

Sequential numbered list items:
 * 1) Foo
 * 2) Bar
 * 3) Baz

Nested ordered and numbered list items:
 * 1) Foo
 * 2) * FooFoo
 * 3) * FooBar
 * 4) Bar
 * 5) BarFoo
 * 6) BarBar
 * 7) BarBarFoo
 * 8) BarBarBar
 * 9) Baz
 * 10) BazFooFoo
 * 11) BazFooBar
 * 12) BazFooBaz
 * 13) BazBar
 * 14) BazBarFoo
 * 15) * BazBarBar
 * 16) * BazBarBaz
 * 17) * BazBarBazFoo
 * 18) * BazBarBazBar
 * 19) * BazBarBazBaz