Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
pagedjs
pagedjs
  • Project
    • Project
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 153
    • Issues 153
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 11
    • Merge Requests 11
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Tools
  • pagedjspagedjs
  • Issues
  • #111

Closed
Open
Opened Apr 19, 2019 by Julien Bidoret@julienbidoret
  • Report abuse
  • New issue
Report abuse New issue

Pagedjs generated content

The usual CSS generated content can combine different chunks of text and data, such as :

a::after {
    content: attr(href) ' — ' attr(data-whatever);
}

Paged.js custom generated content cannot combine chunks like a counter and a element:

@page {
    @bottom-left {
        content: counter(page) ' — ' element(runningTitle);
    }
}

If an element is within the content: rule, it overwrites any other content.

An element can contain html (which is nice) but adding generated content text nodes next to it could be smoother as it resembles more usual CSS behaviour.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
3
Labels
Priority generated content running titles
Assign labels
  • View project labels
Reference: tools/pagedjs#111