Page MenuHomePhabricator

Text inside <span> nested inside other formatting not rendered as continuous span line feeds
Closed, DuplicatePublicBUG REPORT

Description

List of steps to reproduce (step by step, including full links if applicable):

{{hi|{{smaller|ADVANCE OF SETTLEMENT SINCE THE JARDINE EXPEDITION. AIM OF HANN'S EXPEDITION.
PERSONNEL AND EQUIPMENT. PARALLEL CREEK AND EINASLEIGH RIVER. START FROM FOSSILBROOK. CAMP I. SITE OF MODERN LYNDBROOK RAILWAY STATION. DOWN LYND RIVER. CAMPS 2 AND 3. HACKETT'S CREEK. LYND RIVER AGAIN. CAMP 5. KIRCHNER RANGE. PROSPECTING FOR GOLD. PINNACLE CREEK. CAMP 6. TATE RIVER. NONDA CREEK. NATIVES. CAMPS 7, 8 AND 9. WALSH 
RIVER. CAMP 10. EXCURSION UP THE VALLEY. HILLS OF MAGNETIC IRON ORE. NATIVES. MAIN JOURNEY RESUMED. WALSH RIVER. CAMP II. FOSSILS. AN AREA OF LOWER CRETACEOUS ROCKS. MODERN TELEGRAPH LINE AT CAMP 12. ELIZABETH CREEK. O.K. COPPER MINE. WROTHAM PARK CATTLE STATION. NOLAN CREEK. CAMP 13. MITCHELL RIVER. CAMP 14. }}}}
`

What happens?:
A spurious P block is inserted breaking the span of content. (apparently because of line-feeds which are not collapsed)

<div class="hanging-indent" style=""><span style="font-size: 83%;">ADVANCE OF SETTLEMENT SINCE THE JARDINE EXPEDITION. AIM OF HANN'S EXPEDITION. 
<p>PERSONNEL AND EQUIPMENT. PARALLEL CREEK AND EINASLEIGH RIVER. START FROM FOSSILBROOK. CAMP I. SITE OF MODERN LYNDBROOK RAILWAY STATION. DOWN LYND RIVER. CAMPS 2 AND 3. HACKETT'S CREEK. LYND RIVER AGAIN. CAMP 5. KIRCHNER RANGE. PROSPECTING FOR GOLD. PINNACLE CREEK. CAMP 6. TATE RIVER. NONDA CREEK. NATIVES. CAMPS 7, 8 AND 9. WALSH 
</p>
RIVER. CAMP 10. EXCURSION UP THE VALLEY. HILLS OF MAGNETIC IRON ORE. NATIVES. MAIN JOURNEY RESUMED. WALSH RIVER. CAMP II. FOSSILS. AN AREA OF LOWER CRETACEOUS ROCKS. MODERN TELEGRAPH LINE AT CAMP 12. ELIZABETH CREEK. O.K. COPPER MINE. WROTHAM PARK CATTLE STATION. NOLAN CREEK. CAMP 13. MITCHELL RIVER. CAMP 14. </span></div>

What should have happened instead?:
The text should be rendered as a continuous span, WITHOUT a spurious P tag being inserted.

Or

The Linter extension should have generated a warning about the line-feeds inside SPAN based content, so they can be removed.

Event Timeline

Aklapper renamed this task from Text inside SPAN nested inside other formatting not rendered as continuious span line-feeds in input removed... to Text inside <span> nested inside other formatting not rendered as continuous span line feeds.Jul 1 2022, 9:38 AM