mediawiki-extensions-Discus.../modules/dt.ui.NewTopicController.less

.ext-discussiontools-ui-newTopic {
	clear: both;

	&.oo-ui-panelLayout-padded.oo-ui-panelLayout-framed {
		margin-top: 2em;
	}

	h2&-sectionTitle {
		max-width: none;
		// This element is a <h2> - override unwanted heading styles
		padding: 0;
		border: 0;
		margin-top: 4px;
	}

	.ext-discussiontools-ui-replyWidget {
		margin-bottom: 0;
	}

	.oo-ui-fieldLayout-messages {
		max-width: none;
	}
}
Change dt- class prefix to ext-discussiontools- Longer, but follows the style guide and less likely to conflict. We need to account for init classes in the cache being around for a while. Change-Id: I738bc93393850db320fdbda2b003ca8ac40556da 2021-03-13 14:39:39 +00:00			`.ext-discussiontools-ui-newTopic {`
Ability to add new discussion sections 1. Extend the JS modifier to allow adding top-level comments (that is, replies to headings). PHP modifier doesn't do this because we'll save the changes using paction=addtopic instead. 2. Subclass CommentController to allow adding a new heading and a top-level comment underneath it at the same time. 3. A lot of ugly code in ReplyWidget to customize the interface for this case. Much of it should probably be moved to CommentController/NewTopicController. Bug: T267595 Change-Id: I9c707bb7f7aae1b92c72fb4dee436490f8c8409b 2020-08-29 12:00:51 +00:00			`clear: both;`

Padding and border around new topic tool Bug: T269157 Change-Id: I4f56f9dc0eca71ea4ed452df49e861aac47e3de8 2021-01-13 20:54:59 +00:00			`&.oo-ui-panelLayout-padded.oo-ui-panelLayout-framed {`
			`margin-top: 2em;`
			`}`

			`h2&-sectionTitle {`
Ability to add new discussion sections 1. Extend the JS modifier to allow adding top-level comments (that is, replies to headings). PHP modifier doesn't do this because we'll save the changes using paction=addtopic instead. 2. Subclass CommentController to allow adding a new heading and a top-level comment underneath it at the same time. 3. A lot of ugly code in ReplyWidget to customize the interface for this case. Much of it should probably be moved to CommentController/NewTopicController. Bug: T267595 Change-Id: I9c707bb7f7aae1b92c72fb4dee436490f8c8409b 2020-08-29 12:00:51 +00:00			`max-width: none;`
			`// This element is a <h2> - override unwanted heading styles`
			`padding: 0;`
			`border: 0;`
Padding and border around new topic tool Bug: T269157 Change-Id: I4f56f9dc0eca71ea4ed452df49e861aac47e3de8 2021-01-13 20:54:59 +00:00			`margin-top: 4px;`
			`}`

Change dt- class prefix to ext-discussiontools- Longer, but follows the style guide and less likely to conflict. We need to account for init classes in the cache being around for a while. Change-Id: I738bc93393850db320fdbda2b003ca8ac40556da 2021-03-13 14:39:39 +00:00			`.ext-discussiontools-ui-replyWidget {`
Ability to add new discussion sections 1. Extend the JS modifier to allow adding top-level comments (that is, replies to headings). PHP modifier doesn't do this because we'll save the changes using paction=addtopic instead. 2. Subclass CommentController to allow adding a new heading and a top-level comment underneath it at the same time. 3. A lot of ugly code in ReplyWidget to customize the interface for this case. Much of it should probably be moved to CommentController/NewTopicController. Bug: T267595 Change-Id: I9c707bb7f7aae1b92c72fb4dee436490f8c8409b 2020-08-29 12:00:51 +00:00			`margin-bottom: 0;`
			`}`

			`.oo-ui-fieldLayout-messages {`
			`max-width: none;`
			`}`
			`}`