WebPlatform Docs WebPlatformDocs

## LocalSettings.php
<?php

# vi set ai syntax=php

// Managed by Salt Stack, please DO NOT TOUCH, or ALL CHANGES WILL be LOST!

#error_reporting(0);

#
# Redis job servers

## dabblet.css
/**
 * The first commented line is your codelet’s title
 */

p {
	color: #f06;
	font: italic 200% Georgia, serif;
	transition: 1s cubic-bezier(.2,.6,.8,.8);
	width: 400px;
}

## 0_COMPATIBILITY_TABLES_ADJUST_FORM.md

      
              3 files
            
          
              0 forks
            
          
              1 comment
            
          
              0 stars
            
          
                WebPlatformDocs
                / 0_COMPATIBILITY_TABLES_ADJUST_FORM.md
            
            
              Last active
              August 29, 2015 14:04
            
          
    Compatibility tables: Changing forms to use new system

Current situation

We have Template:CSS_Property included in all CSS properties showing output of compatibility tables.
It assumes that the last part of the current page name MATCHES EXACTLY the same thing as inside the compat data JSON file. Which is not ideal.
For example:

/wiki/css/properties/border-radius is fine in compat/data-human.json, search for ":root > .data > .css > .border-radius", but


## dabblet.css
/**
 * attributes example
 */

## dabblet.css
/**
 * navigator.getMedia example
 */

## dabblet.css
/**
 * [object Navigator]
 */

## dabblet.css
/**
 * mousemove event sample... cursor crosshairs.
 */

## dabblet.css
/**
 * mousemove event sample... cursor crosshairs.
 */

## dabblet.css
/**
 * mousemove event sample... cursor crosshairs.
 */

## dabblet.css
/**
 * mouseleave event sample
 */
	<?php

	# vi set ai syntax=php

	// Managed by Salt Stack, please DO NOT TOUCH, or ALL CHANGES WILL be LOST!

	#error_reporting(0);

	#
	# Redis job servers
	/**
	* The first commented line is your codelet’s title
	*/

	p {
	color: #f06;
	font: italic 200% Georgia, serif;
	transition: 1s cubic-bezier(.2,.6,.8,.8);
	width: 400px;
	}