fix: SEO SPA editor last fixes (3/4)

web/src/views/__tests__/EditorSeoSave.spec.ts

@@ -149,6 +149,8 @@ describe('Saving state', () => {
 		expect(fieldByLabel(panel, 'Meta description')!.disabled).toBe(true)
 		expect(fieldByLabel(panel, 'Excerpt')!.disabled).toBe(true)
 		expect(textOf(panel)).toContain('Saving…')
+		expect(fieldByLabel(panel, 'Meta title')!.className).toContain('disabled:opacity-100')
+		expect(fieldByLabel(panel, 'Meta title')!.className).not.toContain('opacity-40')
 		expect(
 			textOf(document.body.querySelector('[data-testid="save-button"]')!.parentElement),
 		).toContain('Save')
@@ -286,6 +288,22 @@ describe('The editor Save button treats SEO edits like any other edit', () => {
 	})
 })
 
+describe('Publish with a clean draft', () => {
+	it('only sends the publish request', async () => {
+		const backend = await mountSeo(seoBackend())
+		backend.responders['PATCH /v1/article/12/publish'] = () => ({
+			...backend.article,
+			is_online: true,
+		})
+		const before = backend.calls.length
+
+		await click('Publish')
+
+		const patches = backend.calls.slice(before).filter((call) => call.method === 'PATCH')
+		expect(patches.map((call) => call.path)).toEqual(['/v1/article/12/publish'])
+	})
+})
+
 describe('Leaving with unsaved SEO edits', () => {
 	it('asks Leave without saving? when the draft holds an unsaved SEO value', async () => {
 		const { panel } = await failedPanelSave()