In Review Board 3.0, we're making some significant changes and clean-ups to the HTML, CSS, and JavaScript for the main review request page. This document details those changes.

HTML/CSS changes

• The .box and .box-inner elements have been removed, since all the built-in styles applied to them were overridden anyway.
• Markup relating to the summary section (review request summary and "Created ...") has been simplified.
• Section labels are now consolidated under a single .review-request-section-label class rather than relying on several different element types.
• Entries on the review request page (reviews and change descriptions) no longer use {% box %}, which means that the .box, .box-container, and .box-inner elements are no longer used. These have been replaced with .review-request-page-entry (which wraps the entire thing) and .review-request-page-entry-contents (which is the actual box with the shadow).
• Class and ID changes:
  • #review_request -> #review-request
  • #review_request_banners -> #review-request-banners
  • .main -> .review-request-body
  • .header -> .review-request-summary
  • .content -> .review-request-section
  • .actions -> .review-request-actions
  • .actions li -> .review-request-action (and .review-request-action-icon)
  • .actions-right-container -> .review-request-actions-right-container
  • .actions-right -> .review-request-actions-right
  • .actions-left -> .review-request-actions-left
  • In the entry headers, .reviewer -> .summary and .posted_time -> .timestamp

JavaScript changes

• In ReviewRequestPageView, ReviewReplyEditorView, and ReviewBoxView, options.pageEditState has been renamed to options.reviewRequestEditor.
• In ReviewRequestPageView and ReviewBoxView, options.editorData has been removed in favor of directly passing in its only entry, options.showSendEmail.
• ReviewBoxListView has been removed and its functionality folded into ReviewRequestPageView. In addition, ReviewBoxView and ChangeBoxView are now expected to be instantiated externally and added to the page rather than by scanning the DOM for relevant items.