Stowage/ladybird
2
0
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2025-10-30 21:01:00 +00:00
Code Issues Projects Releases Packages Wiki Activity
ladybird/Userland/Libraries/LibWeb/StylePropertiesModel.h

52 lines
1.5 KiB
C
Raw Normal View History

Meta: Add license header to source files As suggested by Joshua, this commit adds the 2-clause BSD license as a comment block to the top of every source file. For the first pass, I've just added myself for simplicity. I encourage everyone to add themselves as copyright holders of any file they've added or modified in some significant way. If I've added myself in error somewhere, feel free to replace it with the appropriate copyright holder instead. Going forward, all new source files should include a license header.
2020-01-18 09:38:21 +01:00
/*
* Copyright (c) 2018-2020, Andreas Kling <kling@serenityos.org>
Everywhere: Use my shiny new serenityos.org email :^)
2021-09-03 11:14:37 +01:00
* Copyright (c) 2021, Sam Atkins <atkinssj@serenityos.org>
Meta: Add license header to source files As suggested by Joshua, this commit adds the 2-clause BSD license as a comment block to the top of every source file. For the first pass, I've just added myself for simplicity. I encourage everyone to add themselves as copyright holders of any file they've added or modified in some significant way. If I've added myself in error somewhere, feel free to replace it with the appropriate copyright holder instead. Going forward, all new source files should include a license header.
2020-01-18 09:38:21 +01:00
*
Everything: Move to SPDX license identifiers in all files. SPDX License Identifiers are a more compact / standardized way of representing file license information. See: https://spdx.dev/resources/use/#identifiers This was done with the `ambr` search and replace tool. ambr --no-parent-ignore --key-from-file --rep-from-file key.txt rep.txt *
2021-04-22 01:24:48 -07:00
* SPDX-License-Identifier: BSD-2-Clause
Meta: Add license header to source files As suggested by Joshua, this commit adds the 2-clause BSD license as a comment block to the top of every source file. For the first pass, I've just added myself for simplicity. I encourage everyone to add themselves as copyright holders of any file they've added or modified in some significant way. If I've added myself in error somewhere, feel free to replace it with the appropriate copyright holder instead. Going forward, all new source files should include a license header.
2020-01-18 09:38:21 +01:00
*/
LibWeb: replace some tab characters with spaces also add missing "#pragma once" in StylePropertiesModel.h
2020-05-28 14:20:12 +02:00
#pragma once
LibWeb: Modify StylePropertiesModel to work with JSON Now that the DOM Inspector communicates remotely with the web content, we can't read the `StyleProperties` object from a `Node` directly, but will receive JSON over IPC. This updates the model to match.
2021-08-24 16:27:10 +01:00
#include <AK/JsonObject.h>
LibGUI: Remove leading G from filenames
2020-02-06 20:33:02 +01:00
#include <LibGUI/Model.h>
Libraries: Add missing headers A C++ source file containing just #include <LibFoo/Bar.h> should always compile cleanly. This patch adds missing header inclusions that could have caused weird error messages if they were used in a different context. Also, this confused QtCreator.
2021-01-21 20:55:37 +01:00
#include <LibWeb/CSS/StyleProperties.h>
Browser+LibHTML: Add "Computed" styles to the DOM inspector I though it would be nice to also show the style that the browser uses to display an element. In order to do that, in place of the styles table I've put a tab widget, with tabs for both element and computed element styles.
2020-01-03 04:15:50 +01:00
LibWeb: Move everything into the Web namespace
2020-03-07 10:27:02 +01:00
namespace Web {
LibGUI: Put all classes in the GUI namespace and remove the leading G This took me a moment. Welcome to the new world of GUI::Widget! :^)
2020-02-02 15:07:41 +01:00
class StylePropertiesModel final : public GUI::Model {
Browser+LibHTML: Add "Computed" styles to the DOM inspector I though it would be nice to also show the style that the browser uses to display an element. In order to do that, in place of the styles table I've put a tab widget, with tabs for both element and computed element styles.
2020-01-03 04:15:50 +01:00
public:
enum Column {
PropertyName,
PropertyValue,
__Count
};
LibWeb: Modify StylePropertiesModel to work with JSON Now that the DOM Inspector communicates remotely with the web content, we can't read the `StyleProperties` object from a `Node` directly, but will receive JSON over IPC. This updates the model to match.
2021-08-24 16:27:10 +01:00
static NonnullRefPtr<StylePropertiesModel> create(StringView properties)
{
AK: Make JSON parser return ErrorOr<JsonValue> (instead of Optional) Also add slightly richer parse errors now that we can include a string literal with returned errors. This will allow us to use TRY() when working with JSON data.
2021-11-15 01:46:51 +01:00
auto json_or_error = JsonValue::from_string(properties).release_value_but_fixme_should_propagate_errors();
return adopt_ref(*new StylePropertiesModel(json_or_error.as_object()));
LibWeb: Modify StylePropertiesModel to work with JSON Now that the DOM Inspector communicates remotely with the web content, we can't read the `StyleProperties` object from a `Node` directly, but will receive JSON over IPC. This updates the model to match.
2021-08-24 16:27:10 +01:00
}
virtual ~StylePropertiesModel() override;
Browser+LibHTML: Add "Computed" styles to the DOM inspector I though it would be nice to also show the style that the browser uses to display an element. In order to do that, in place of the styles table I've put a tab widget, with tabs for both element and computed element styles.
2020-01-03 04:15:50 +01:00
LibWeb: Modify StylePropertiesModel to work with JSON Now that the DOM Inspector communicates remotely with the web content, we can't read the `StyleProperties` object from a `Node` directly, but will receive JSON over IPC. This updates the model to match.
2021-08-24 16:27:10 +01:00
virtual int row_count(GUI::ModelIndex const& = GUI::ModelIndex()) const override;
virtual int column_count(GUI::ModelIndex const& = GUI::ModelIndex()) const override { return Column::__Count; }
Browser+LibHTML: Add "Computed" styles to the DOM inspector I though it would be nice to also show the style that the browser uses to display an element. In order to do that, in place of the styles table I've put a tab widget, with tabs for both element and computed element styles.
2020-01-03 04:15:50 +01:00
virtual String column_name(int) const override;
LibWeb: Modify StylePropertiesModel to work with JSON Now that the DOM Inspector communicates remotely with the web content, we can't read the `StyleProperties` object from a `Node` directly, but will receive JSON over IPC. This updates the model to match.
2021-08-24 16:27:10 +01:00
virtual GUI::Variant data(GUI::ModelIndex const&, GUI::ModelRole) const override;
Browser: Allow jumping to stylenames by typing in the inspector This adds the default behavior of search and highlighting of abstractView to the inspectorWidget. Search results are based on the titles in the first columns.
2022-02-17 18:20:20 +01:00
virtual bool is_searchable() const override { return true; }
virtual Vector<GUI::ModelIndex> matches(StringView, unsigned flags, GUI::ModelIndex const&) override;
Browser+LibHTML: Add "Computed" styles to the DOM inspector I though it would be nice to also show the style that the browser uses to display an element. In order to do that, in place of the styles table I've put a tab widget, with tabs for both element and computed element styles.
2020-01-03 04:15:50 +01:00
private:
LibWeb: Modify StylePropertiesModel to work with JSON Now that the DOM Inspector communicates remotely with the web content, we can't read the `StyleProperties` object from a `Node` directly, but will receive JSON over IPC. This updates the model to match.
2021-08-24 16:27:10 +01:00
explicit StylePropertiesModel(JsonObject);
Browser+LibHTML: Add "Computed" styles to the DOM inspector I though it would be nice to also show the style that the browser uses to display an element. In order to do that, in place of the styles table I've put a tab widget, with tabs for both element and computed element styles.
2020-01-03 04:15:50 +01:00
LibWeb: Modify StylePropertiesModel to work with JSON Now that the DOM Inspector communicates remotely with the web content, we can't read the `StyleProperties` object from a `Node` directly, but will receive JSON over IPC. This updates the model to match.
2021-08-24 16:27:10 +01:00
JsonObject m_properties;
Browser+LibHTML: Add "Computed" styles to the DOM inspector I though it would be nice to also show the style that the browser uses to display an element. In order to do that, in place of the styles table I've put a tab widget, with tabs for both element and computed element styles.
2020-01-03 04:15:50 +01:00
struct Value {
String name;
String value;
};
Vector<Value> m_values;
};
LibWeb: Move everything into the Web namespace
2020-03-07 10:27:02 +01:00
}
Reference in a new issue Copy permalink