Source for the Bugzilla Tracker script used on W3C proposals
Switch branches/tags
Nothing to show
Pull request Compare This branch is even with oslego:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
mock
scripts
style
test
README.md

README.md

W3C BugzillaTracker

W3C BugzillaTracker makes it easier for editors to keep track of bugs opened for their proposals. The script handles synchronizing bugs between the W3C Bugzilla instance and the bug data embedded into the W3C documents.

A bug dashboard is layered on top of the W3C spec with notable bug changes: new, updated or resolved.

Usage

1 Include the required files

    <link rel="stylesheet" type="text/css" href="style/issues.css">
    <script type="text/javascript" src="scripts/BugzillaTrackerUtil.js"></script>
    <script type="text/javascript" src="scripts/BugzillaTracker.js"></script>  

2 Add the bug template to the document

<script type="text/template" id="issue-template">
    <div class="issue-marker" data-bug_id="{{bug_id}}" data-bug_status="{{bug_status}}">
    <a href="https://www.w3.org/Bugs/Public/show_bug.cgi?id={{bug_id}}">Bug-{{bug_id}}</a>
    <div class="issue-details">
        <p class="short-desc">{{short_desc}}</p>
    </div>  
    </div>
</script> 

Important
The bugs hardcoded in the document need to follow the same template.

3 Call the script with the desired product and component

<script type="text/javascript">
    // product = "CSS"
    // component = "Regions"
    checkSpecificationIssues('CSS', 'Regions');        
</script>    

Browser requirements

The script is expected to work in Google Chrome, Safari, Firefox, Opera and Internet Explorer 9+