diff --git a/CHANGELOG.md b/CHANGELOG.md
index 97965f180..70aa21e17 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,3 +1,13 @@
+## 0.16.26-dev1
+
+### Enhancements
+
+- **Add support for images in html partitioner** `![]()
` tags will now be parsed as `Image` elements. When `extract_image_block_types` includes `Image` and `extract_image_block_to_payload`=True then the `image_base64` will be included for images that specify the base64 data (rather than url) as the source.
+
+### Features
+
+### Fixes
+
## 0.16.25
### Enhancements
diff --git a/test_unstructured/partition/html/test_partition.py b/test_unstructured/partition/html/test_partition.py
index 0ca830eec..4df535319 100644
--- a/test_unstructured/partition/html/test_partition.py
+++ b/test_unstructured/partition/html/test_partition.py
@@ -6,7 +6,7 @@ from __future__ import annotations
import io
import pathlib
-from typing import Any
+from typing import Any, Optional
import pytest
from lxml import etree
@@ -24,6 +24,7 @@ from unstructured.cleaners.core import clean_extra_whitespace
from unstructured.documents.elements import (
Address,
CompositeElement,
+ ElementType,
ListItem,
NarrativeText,
Table,
@@ -296,6 +297,68 @@ def test_it_does_not_extract_text_in_style_tags():
assert element.text == "Lorem ipsum dolor"
+# -- image parsing behaviors ---------------------------------------------------------------------
+
+
+@pytest.mark.parametrize(
+ ("extract_to_payload", "extract_types", "expect_base64"),
+ [
+ (True, ["Image"], True),
+ (True, [], False),
+ (True, None, False),
+ (False, ["Image"], False),
+ ],
+)
+def test_partition_html_base64_for_images(
+ opts_args: dict[str, Any],
+ extract_to_payload: bool,
+ extract_types: Optional[list[str]],
+ expect_base64: bool,
+):
+ base64 = (
+ "iVBORw0KGgoAAAANSUhEUgAAAAUAAAAFCAYAAACNbyblAAAAHElEQVQI12P4//8/"
+ "w38GIAXDIBKE0DHxgljNBAAO9TXL0Y4OHwAAAABJRU5ErkJggg=="
+ )
+ src = "data:image/png;base64," + base64
+ alt_text = "Base64 Image"
+
+ html = f"""
+
+
+
+
+
The overview is the first page visitors will see when they visit your space, so it helps to include some information on what the space is about and what your team is working on.
-
+ ![]()
+
Add a header image. This gives your overview visual appeal and makes it welcoming for visitors.
-
+
Explain what the space is for. Start by summarizing the purpose of the space. This could be your team's mission statement or a brief description of the kind of work you do.
-
+
Share team goals. Add links to your team's OKRs, project plans, and product roadmaps so visitors can quickly get a sense of your team's goals.
-
+
Tell people how to contact you. Share your timezone and links to Slack channels, email aliases, or other contact details your team uses so visitors can contact you with questions or feedback about your team's work.
-
+
Use shortcuts for easy access
-
+
Shortcuts are helpful for important pages that members of a space might need to get to often. These shortcuts are added and organized by the space administrator. Space admins can link to pages in the space, other related spaces, or relevant external web content as well as reorder the shortcuts as needed.
-
+ ![]()
+
πStart discussions with inline comments
-
+
Thoughtful responses can get lost and lose context as email replies pile up. And if you neglect to copy someone or want to add them later on, it's difficult for them to get up to speed. Inline comments allow anyone (or everyone) to huddle around an idea while referencing key information on the project page.
-
+
To leave an inline comment, highlight text on the page and the comment icon will appear.
-
+ ![]()
+
Team members with permission to access the page can respond to any comment. Plus, when a comment thread comes to its natural conclusion, comments can be resolved and cleared away.
-
+
πLoop in team members with @mentions
-
+
@mentions on Confluence function like @mentions on social media platforms like Twitter, Instagram, and Slack. Type the @ symbol on a Confluence page or in a comment, begin spelling a team member's first name, and a list will appear. Select the individual to ask a question or assign a task.
-
+ ![]()
+
πEndorse ideas with reactions
-
+
Use reactions when you want to support a comment or acknowledge you've seen one without clogging up the thread with another comment.
-
+
You can also use reactions on a page or blog post. The author of the content will be notified, and if enough team members react or add comments to the content, it'll be surfaced on Confluence home feed
-
+ ![]()
+
Take your Confluence space to the next level
-
+
Extend the capabilities of your Confluence pages by adding extra functionality or including dynamic content.
-
+
To add functionality:
-
+
Type ' / ' to open the list of items available to use
-
+
Find the item to be inserted and select it
-
+
Select Insert
-
+ ![]()
+
Useful elements for Team space
-
+
Introduce the team
-
+
Add user profiles to display a short summary of a given Confluence user's profile with their role, profile photo and contact details.
-
+ ![]()
+ ![]()
+
Share news and announcements with your team
-
+
Display a stream of latest blog posts so your team can easily see what's been going on.
-
+
Display a list of important pages
-
+
Paste in page URLs to create smart links, or use the content report table to create a list of all the pages in the space.
+ ![]()