gsantner / gsantner/markor

catered version displaying codeblocks in markdown format cannot be disabled or modified if at least one of the codeblock on page is created using (three) backticks

Open
#2,899 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
6.1k
Forks
537
Avg merge
1d 18h
Merged PRs (30d)
4

Description

### ⚠️ This issue respects the following points: ⚠️

- [x] This is a **bug**. Not a [question or feature request](https://github.com/gsantner/markor/issues/new/choose).
- [x] The topic is **not** already reported at [Issues](https://github.com/gsantner/markor/issues?q=#js-issues-search). _(I've searched it and checked most recent issues)_.
- [x] Markor **is** up to date. See [Releases](https://github.com/gsantner/markor/tags) for the latest version. Updates are available from [F-Droid](https://f-droid.org/en/packages/net.gsantner.markor/) and GitHub.
- [x] The bug is still present in the latest development version (git master). (Please [download](https://nightly.link/gsantner/markor/workflows/build-android-project/master) and try the test version of Markor, named **Marder**. Don't worry; Markor and Marder appear as completely separate applications. You can install both side-by-side, and Markor settings are not touched. In case the issue is resolved there, you don't need to create a bug report. The change will be part of the next Markor update.)

### Description

Current behaviour:
- It is impossible to change the layout of the code blocks into other code rendering than styled by Markor using css style rules that are entered into either the head section or the body section, via **Settings** > **View Mode**, or directly on the page, if at least one of the codeblocks is created using backticks ` ``` `.

Expected behaviour:
- The code blocks are rendered in monospace, like now, without expanding the font-size, wrapping its lines or giving the block a copy functionality, if there is not an option to disable all this.
- A possibility exists to style code blocks using css style rules.
- Above behaviour goes for all code blocks, whether they are created using either ` ``` `, the `

` tags or by indenting the string.

### Steps to reproduce

1. enter css style rules using `code` or `pre>code` as selectors aimed at layout changes from the original style rules into head section via **More** > **Settings** > **View Mode**, under _Inject_ via **Inject - > head**
2. enter css style rules using `code` or `pre>code` as selectors aimed at layout changes from the original style rules into body section via **More** > **Settings** > **View Mode**, under _Inject_ **Inject - > body**
3. enter css style rules using `code` or `pre>code` as selectors aimed at layout changes from the original style rules into a html `` tag directly on page
4. create three code blocks on a page using three backticks ` ``` `, the `<pre><code>` tags and by indenting the string.
5. notice thechange in the rendering of the blocks when the codeblock created by using three backticks is deleted.

### Information

Android version: 16
Device (phone model): Samsung S25FE
App Version: v2.16 (163)

### Source

F-Droid

### Format / File type

Markdown

### Additional info / Log

- although not installed marder to check the issue reviewed the changes since the latest version on github, no change was mentioned.
- thank you for and compliments on the application

Contributor guide

No contributing guide indexed for this repository

Research direction

Reproduce the issue in Markor's More > Settings > View Mode injection settings with Markdown code blocks made using backticks, pre/code tags, and indentation. Trace the code-block rendering path from the Markdown preview and verify that injected CSS can style all three forms without unwanted font expansion, wrapping, or copy functionality when those options are disabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java, markdown
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.